agentleFS
Sign inStart free
krishnamallamkrishnamallam/upbox/.claude/skills/refactor/SKILL.md

refactor

Skill2 starsChanged 6 months agoMITView on GitHub

Safely refactor code with test coverage as a safety net

196 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, agent-context-isolation and 9 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

  • 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

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 9

    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:

    Read the code and its tests

    line 13
  2. Distinctive:

    If there are no tests, WRITE TESTS FIRST.

    line 15
  3. Distinctive:

    Check: does this change any external behavior?

    line 20
  4. Distinctive:

    Run tests after EACH step.

    line 24
  5. Distinctive:

    If a test breaks, undo the last step and make a smaller change

    line 25
  6. Distinctive:

    All existing tests pass

    line 28
  7. Distinctive:

    If you can't run the tests, don't refactor

    line 34
  8. Distinctive:

    Never mix refactoring with behavior changes in the same commit

    line 35
  9. Distinctive:

    If the refactoring is large (10+ files), break it into multiple commits

    line 36

“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 $ARGUMENTS safely.

Process

1. Understand the current state

  • Read the code and its tests
  • Identify what the code does, its callers, and its dependencies
  • If there are no tests, WRITE TESTS FIRST. You need a safety net before changing anything

2. Plan the refactoring

  • State what you're changing and why (clearer naming, reduced duplication, better structure)
  • List the specific transformations (extract function, inline variable, move module, etc.)
  • Check: does this change any external behavior? If yes, this isn't a refactor. Reconsider.

3. Make changes in small, testable steps

  • One transformation at a time
  • Run tests after EACH step. Not at the end
  • If a test breaks, undo the last step and make a smaller change

4. Verify

  • All existing tests pass
  • Lint and typecheck pass
  • The public API hasn't changed (unless that was the explicit goal)
  • The code is objectively simpler. Fewer lines, fewer branches, clearer names

Rules

  • If you can't run the tests, don't refactor
  • Never mix refactoring with behavior changes in the same commit
  • If the refactoring is large (10+ files), break it into multiple commits

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