agentleFS
adventurewave-labsadventurewave-labs/apsl-core/skills/refactor/SKILL.md

refactor

Skill0 starsChanged 4 months agoMITView on GitHub

Improve code quality, structure, or readability without changing observable behavior. Use for cleanup, DRY improvements, naming, extraction, reorganization. Supports --goal "description", --scope function|file|module, --auto.

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

Files
SKILL.md

refactor — Refactoring Skill

Prime directive: Never change observable behavior. If a change would alter behavior, flag it and ask.

Execution Steps

  1. Read target and understand the current implementation.
  2. Check context — run git diff HEAD to understand recent changes.
  3. If --goal provided — focus all refactoring toward that specific goal.
  4. Identify opportunities:
    • Duplicated logic that could be extracted into shared functions
    • Functions longer than 40 lines doing more than one thing
    • Unclear names (variables, functions, classes)
    • Missing abstractions for repeated patterns
    • Dead code, commented-out blocks
  5. Show diff first (unless --auto) — present proposed changes as a unified diff.
  6. Wait for approval unless --auto is set.
  7. Apply changes and verify the test suite if one exists.

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.