agentleFS
Sign inStart free
JordanCoinJordanCoin/codemap/.claude/skills/refactor/SKILL.md

refactor

Skill710 starsChanged 8 months agoMITView on GitHub

Safe refactoring with dependency awareness. Use when restructuring, renaming, moving, extracting, or consolidating code.

196 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

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run codemap --deps . to understand the dependency graph

    line 10
  2. Very specific:

    Run codemap --diff to see what's already changed on this branch

    line 12
  3. Distinctive:

    Add the new name alongside the old (alias/wrapper)

    line 24
  4. Distinctive:

    Update all callers to use the new name

    line 25
  5. Distinctive:

    Remove the old name

    line 26
  6. Distinctive:

    Run full test suite

    line 27
  7. Distinctive:

    Create the new file with the same API

    line 31
  8. Distinctive:

    Update all importers to use the new path

    line 33
  9. Distinctive:

    Remove the old file and re-export

    line 34
  10. Very specific:

    Run codemap --deps . again to verify the graph is clean

    line 38
  11. Very specific:

    Run codemap --importers <moved-file> to check nothing is broken

    line 39

“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

Safe Refactoring with Code Intelligence

Before refactoring

  1. Run codemap --deps . to understand the dependency graph
  2. Identify hub files in the refactoring scope: they need extra care
  3. Run codemap --diff to see what's already changed on this branch

Refactoring checklist

  • All tests pass before starting
  • Hub files identified and dependents listed
  • Public API changes planned (additive preferred)
  • Import paths updated if moving files
  • No circular dependencies introduced

Safe rename pattern

  1. Add the new name alongside the old (alias/wrapper)
  2. Update all callers to use the new name
  3. Remove the old name
  4. Run full test suite

Safe move pattern

  1. Create the new file with the same API
  2. Re-export from the old location (temporary)
  3. Update all importers to use the new path
  4. Remove the old file and re-export

After refactoring

  • Run codemap --deps . again to verify the graph is clean
  • Run codemap --importers <moved-file> to check nothing is broken
  • Full test suite must pass

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