Agent skill

Maintainable Code for iPolloWork

by Devin-AXIS in Devin-AXIS/iPolloWork

A code-change gate for the iPolloWork repository: search and reuse first, keep one source of truth, justify every new file or dependency, and audit the change.

Custom licenceAuto-check passedDevelopment

Install Maintainable Code for iPolloWork

skills CLI
$ npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Devin-AXIS/iPolloWork ipollowork-maintainable-code --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/ipollowork-maintainable-code .claude/skills/ipollowork-maintainable-code && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ipollowork-maintainable-code
GitHub stars
6.7k
Token cost
~2.7k tokens
SKILL.md length
1,361 words
Files
4 (incl. scripts, references)
Skills in repo
30
Repo updated
First seen
Licence
Custom licence

At a glance

A code-change gate for the iPolloWork repository: search and reuse first, keep one source of truth, justify every new file or dependency, and audit the change.

  • Works in 9 steps: Find the repository root. Read… → Read references/repository-boundaries.md… → Define a change budget before editing:… → …
  • Having the agent add a feature in the iPolloWork repository
  • SKILL.md covers Non-Negotiable Outcomes, Required Workflow, Creation Gate and Reuse Decision, plus 7 more sections
  • Runs JavaScript scripts from its folder; calls node and git

What it does

The skill asks for the smallest coherent diff, using current platform patterns, bounded runtime cost and one clear owner for each behavior. Before editing, the agent finds the repository root, reads `AGENTS.md`, the owning package manifest, the real entrypoint and nearby implementations, and reads `references/repository-boundaries.md` before adding any file, directory, dependency, API, table or cross-package import. It sets a change budget in which every new-item category defaults to zero.

Searching with `rg` comes before creating anything, covering UI components, the target domain, server sources and shared type and UI packages. The agent then states a reuse decision: reuse unchanged, extend compatibly, extract for real multiple consumers, or create as a last resort, with a reason for each new file or dependency. Replaced code is removed in the same change, leaving no old, v2 or fallback copies, and tests go at the owning layer. A bundled `scripts/audit-changes.mjs` supports the final audit.

When your agent uses it

  • Having the agent add a feature in the iPolloWork repository
  • Refactoring or deleting code without leaving duplicate implementations
  • Checking whether a new file or dependency is really needed

Example prompts

  • “Add a retry option to the server's export route, reusing what already exists.”
  • “Before adding this new dependency, tell me whether an existing package in the repo already covers it.”
  • “Audit my current changes for leftover old or v2 copies and parallel implementations.”

Requirements

  • Node to run the `scripts/audit-changes.mjs` audit script
  • A checkout of the iPolloWork repository

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Find the repository root. Read AGENTS.md, the owning package manifest, the real entrypoint, and nearby implementations.
  2. Read references/repository-boundaries.md before adding a file, directory, dependency, API, table, or cross-package import.
  3. Define a change budget before editing: intended behavior, owning module, expected files touched, and whether any new file, directory…
  4. Search before creating anything
  5. State the reuse decision: reuse unchanged, extend compatibly, extract for real multiple consumers, or create as the last choice. For each…
  6. Implement locally. Remove the replaced path in the same change; do not leave old, new, v2, fallback, or dead compatibility copies behind.
  7. Add focused tests at the owning layer. Do not duplicate server business logic, contracts, state, or validation in the desktop app.
  8. Run the narrow package checks, inspect the complete diff, then run
  9. Resolve every error. Fix warnings or give a concrete ownership/performance reason for keeping the exception.

What it can do on your machine

Read from SKILL.md and the folder at commit 71a74ad. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Maintainable Code for iPolloWork loads about 2.7k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 1,361 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~136
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,361 words (~2,688 tokens).

“Treat this as the repository's single code-quality Skill. Implement changes with the smallest coherent diff, modern platform patterns, bounded runtime cost, and one clear owner. Search and reuse before creating anything.”

— opening of SKILL.md by Devin-AXIS, Custom licence
name
ipollowork-maintainable-code

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (scripts, references) in .codex/skills/ipollowork-maintainable-code of Devin-AXIS/iPolloWork.

  • SKILL.md
  • agents/openai.yaml
  • references/repository-boundaries.md
  • scripts/audit-changes.mjs

Open the folder on GitHubat commit 71a74ad

Compare with similar skills

Maintainable Code for iPolloWork next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Maintainable Code for iPolloWork compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Maintainable Code for iPolloWork this skillDevin-AXIS/iPolloWork6.7k—~2.7kAutomated safety check: PassCustom licence
Dignified Python Standardsdocling-project/docling68k—~1.5kAutomated safety check: PassApache-2.0
Clean Code GuardamElnagdy/guard-skills1.3k2 repos~4.3kAutomated safety check: PassMIT
Cyclomatic Complexitysaurabhkumar8112/cyclomatic-complexity-skill405—~761Automated safety check: PassApache-2.0
Code ReviewerYikai-Liao/symusic1891 repos~1.3kAutomated safety check: PassMIT
QML Coding Best Practicesx-tools-author/x-tools1.1k1 repos~3.4kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Dignified Python Standards

    docling-project/docling

    Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.

    68k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Clean Code Guard

    amElnagdy/guard-skills

    Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.

    1.3k GitHub starsUsed in 2 repos~4.3k tokens
    DevelopmentAuto-check passed
  • Cyclomatic Complexity

    saurabhkumar8112/cyclomatic-complexity-skill

    Refactor code to reduce cyclomatic complexity so it stays readable, maintainable, and aligned with the long-term vision of the codebase, not just optimized for AI comprehension.

    405 GitHub stars~761 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Code Reviewer

    Yikai-Liao/symusic

    Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then…

    189 GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed
  • QML Coding Best Practices

    x-tools-author/x-tools

    Applies QML best practices when writing, reviewing, refactoring or debugging QML code, with Qt 5 and Qt 6 import rules and concise, rule-silent output.

    1.1k GitHub starsUsed in 1 repo~3.4k tokens
    DevelopmentAuto-check passed
  • Brooks Review

    hyhmrright/brooks-lint

    PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books.

    1.5k GitHub starsUsed in 1 repo~430 tokens
    DevelopmentAuto-check passed

More from Devin-AXIS/iPolloWork

All 30 skills in this repo
  • Reproduces iPolloWork enterprise TLS behavior in a Daytona Windows sandbox by installing a fake corporate CA and proving the app and its runtimes use the OS trust store.

    6.7k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Build iPolloWork Templates

    Devin-AXIS/iPolloWork

    Builds a reusable iPolloWork template for Design, Slides or PPT, or HyperFrames Video through conversation, keeping a manifest, reusable variables and a validated package current.

    6.7k GitHub stars~925 tokensUpdated yesterday
    Auto-check passed
  • OpenCode Plugin Creator

    Devin-AXIS/iPolloWork

    Scaffolds an OpenCode plugin for iPolloWork with the right async factory shape, zod-based tool definitions and hook registration, and explains where to place and register it.

    6.7k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Agent-First Screenshots

    Devin-AXIS/iPolloWork

    Has an agent drive the real app through CDP and capture clean, defect-free product screenshots, gated by DOM, pixel and vision checks in a loop.

    6.7k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Daytona Chrome CDP

    Devin-AXIS/iPolloWork

    Launches a standalone Chrome or Chromium in a Daytona sandbox and drives it over CDP for web sign-in, OAuth and other flows that should bypass the Electron app.

    6.7k GitHub stars~582 tokensUpdated yesterday
    Auto-check passed
  • Daytona Cloud Server Setup

    Devin-AXIS/iPolloWork

    Starts the hosted server side of iPolloWork in a Daytona sandbox, running Den Web, Den API, the worker proxy and MySQL for end-to-end cloud testing.

    6.7k GitHub stars~687 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Maintainable Code for iPolloWork

What does Maintainable Code for iPolloWork do?

A code-change gate for the iPolloWork repository: search and reuse first, keep one source of truth, justify every new file or dependency, and audit the change. The skill asks for the smallest coherent diff, using current platform patterns, bounded runtime cost and one clear owner for each behavior.md` before adding any file, directory, dependency, API, table or cross-package import.

When should I use Maintainable Code for iPolloWork?

Maintainable Code for iPolloWork fits situations like: having the agent add a feature in the iPolloWork repository; refactoring or deleting code without leaving duplicate implementations; checking whether a new file or dependency is really needed.

How do I install Maintainable Code for iPolloWork in Claude Code?

Run `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -a claude-code`. Or copy the skill folder (.codex/skills/ipollowork-maintainable-code in Devin-AXIS/iPolloWork) into .claude/skills/ipollowork-maintainable-code in your project. Claude Code loads it when a task matches its description.

How do I install Maintainable Code for iPolloWork in Codex?

Run `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -a codex`. Or copy the skill folder (.codex/skills/ipollowork-maintainable-code in Devin-AXIS/iPolloWork) into .agents/skills/ipollowork-maintainable-code in your project. Codex loads it when a task matches its description.

Can I use Maintainable Code for iPolloWork in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Devin-AXIS/iPolloWork --skill ipollowork-maintainable-code -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ipollowork-maintainable-code, .gemini/skills/ipollowork-maintainable-code, .github/skills/ipollowork-maintainable-code and .opencode/skills/ipollowork-maintainable-code in your project.

What does Maintainable Code for iPolloWork need to run?

Going by SKILL.md and its folder, Maintainable Code for iPolloWork needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and git). Our summary lists: Node to run the `scripts/audit-changes.mjs` audit script; A checkout of the iPolloWork repository.

Does Maintainable Code for iPolloWork access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Maintainable Code for iPolloWork safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Maintainable Code for iPolloWork use?

Maintainable Code for iPolloWork has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Maintainable Code for iPolloWork use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Maintainable Code for iPolloWork?

Skills that share tags, products or a category with Maintainable Code for iPolloWork: Dignified Python Standards (docling-project/docling, 68k stars), Clean Code Guard (amElnagdy/guard-skills, 1.3k stars), Cyclomatic Complexity (saurabhkumar8112/cyclomatic-complexity-skill, 405 stars) and Code Reviewer (Yikai-Liao/symusic, 189 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Maintainable Code for iPolloWork?

Devin-AXIS (a GitHub user) maintains it in Devin-AXIS/iPolloWork, which has 6,717 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 6, 2026.

Source: Devin-AXIS/iPolloWork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.