agentleFS
Sign inStart free
carlokopcarlokop/skills/refactor/SKILL.md

refactor

Skill0 starsChanged 53 days agoMITView on GitHub

Auditeert git-wijzigingen sinds de laatste gemergede PR op refactor-kansen (dode code, god components, grote functies, smells), schrijft rapport naar docs/reports/, plant taken, commit rapport, voert refactors per taak uit met commits, en eindigt met npm-test skill. Gebruik wanneer de gebruiker refactor skill, post-PR refactor audit, of /reports refactor-audit vraagt.

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, debug-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • zebbernSkill

    debug-fix

    Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

    Also in 4 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • parcadeiSkill

    agentica-infrastructure

    Reference guide for Agentica multi-agent infrastructure APIs

    Also in 3 projects that use this

  • +8 more from parcadei

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Commit alleen het rapport (+ skill indien nieuw):

    line 48

“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Refactor

Workflow voor wijzigingen zonder open PR op de huidige branch.

Fase 1 — Scope (geen code wijzigen)

  1. Bepaal basiscommit:
    • gh pr list --state merged --limit 1 op de branch, of
    • mergeCommit / headRefOid van de laatste gemergede PR voor deze branch.
  2. Diff: git log <base>..HEAD --oneline en git diff <base>..HEAD --stat.
  3. Open PR check: gh pr list --head $(git branch --show-current) — als open PR bestaat, stop en meld dat audit op PR-diff moet.

Fase 2 — Audit (high effort)

Review alle gewijzigde react/src, node/src, en relevante router/layout/lib in de diff.

Checklist:

  • Dode code, ongebruikte exports, deprecated aliassen
  • God components/pages (>250 regels, veel state, mixed concerns)
  • Functies >40 regels met meerdere verantwoordelijkheden
  • Duplicatie (nav-filter, load/save hooks, validators)
  • Regressies (bijv. nav active state na shell-wijziging)
  • RBAC/route/sync tussen React en Node
  • Tests ontbreken voor gedrag dat refactored wordt

Geen productfeatures of scope-uitbreiding — alleen onderhoudbaarheid.

Fase 3 — Rapport

Schrijf naar docs/reports/refactor-audit-post-PR-<n>-<branch-slug>.md (zelfde stijl als refactor-audit-PR-41-*.md):

  • Context (basiscommit, commits, geen open PR)
  • Findings F1…Fn (severity, files, smell, recommendation)
  • Ordered task plan (R1, R2, …) — elke taak één commit
  • Out of scope

Commit alleen het rapport (+ skill indien nieuw):

git add docs/reports/ .cursor/skills/refactor/
git commit -m "$(cat <<'EOF'
docs: refactor audit sinds PR #<n>

EOF
)"

Fase 4 — Refactor per taak

Voor elke taak Rn in volgorde:

  1. Implementeer minimale correcte diff
  2. Unit/integration tests bij gedragswijziging
  3. npm run test in react/ of node/ indien gelimiteerd; anders volledige npm-test skill aan het eind
  4. Commit:
git commit -m "$(cat <<'EOF'
refactor(<scope>): <korte why>

EOF
)"

Fase 5 — Validatie

Lees en volg .cursor/skills/npm-test/SKILL.md: test → lint → build tot groen.

Regels

  • Volg project rules (forbidden-patterns, testing, design-guidelines waar UI raakt)
  • Geen push tenzij gebruiker vraagt
  • Rapport vóór refactor-commits

Gerelateerd

  • npm-test
  • Voorbeeldrapport: docs/reports/refactor-audit-PR-41-periodieke_factuur_aanpassen.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free