agentleFS
nwiizonwiizo/claudelytics/.claude/skills/refactor/SKILL.md

refactor

Skill88 starsChanged 8 months agoMITView on GitHub

Systematic code refactoring - analysis, pattern detection, incremental changes with verification. Use for code improvement and tech debt reduction.

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

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a focused commit

    line 40
  2. Very specific:

    Run tests after each change: cargo test

    line 41
  3. Distinctive:

    Verify no behavior changes

    line 42
  4. Distinctive:

    Update documentation if needed

    line 43
  5. Distinctive:

    Never change behavior and refactor in the same commit

    line 55
  6. Distinctive:

    Run tests after every change

    line 56
  7. Distinctive:

    Keep commits small and focused

    line 57
  8. Distinctive:

    If unsure about a refactoring, ask before proceeding

    line 58

“Common” is measured: kept by at least 6 in 10 of the 168 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

Code Refactoring Workflow

Refactor target: $ARGUMENTS

Step 1: Code Analysis (parallel)

cargo clippy -- -W clippy::all -W clippy::pedantic
tokei src/
rg "TODO|FIXME|HACK" src/

Step 2: Pattern Detection

Identify these code smells:

  • Duplicate code: Similar logic in multiple places
  • Long functions: Functions > 50 lines
  • Complex types: Structs with > 10 fields
  • Deep nesting: > 3 levels of indentation
  • Magic numbers: Hardcoded values without constants
  • Inconsistent error handling: Mixed error patterns

Step 3: Refactoring Plan

Prioritize targets and plan changes:

  1. Module organization (split large files)
  2. Function decomposition (single responsibility)
  3. Type safety improvements (enums over strings, newtypes)
  4. Performance optimizations (iterators, reduce allocations)

Step 4: Incremental Refactoring

For each change:

  1. Create a focused commit
  2. Run tests after each change: cargo test
  3. Verify no behavior changes
  4. Update documentation if needed

Step 5: Verification

cargo test
cargo clippy -- -D warnings
git diff --stat

Guidelines

  • Never change behavior and refactor in the same commit
  • Run tests after every change
  • Keep commits small and focused
  • If unsure about a refactoring, ask before proceeding

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.