agentleFS
Sign inStart free
asymmetric-effortasymmetric-effort/convocate/.claude/skills/refactor-safely/SKILL.md

refactor-safely

Skill4 starsChanged 4 months agoMITView on GitHub

Plan and execute safe refactoring using dependency analysis

21 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 audit-test-suite, change-data-safely 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.
  • yaohuangguanSkill

    audit-test-suite

    Find where an existing test suite is weak and decide what to test next, ranked by risk. Use this when asked to add missing tests, find gaps, raise coverage, assess test quality or see which areas are thin, even if the request only mentions a coverage percentage.

    Also in 3 projects that use this

  • yaohuangguanSkill

    change-data-safely

    Change a database schema or stored data without breaking running code or losing data. Use this for any migration, new or changed column, backfill, bulk update, delete, index, or change to a stored format, including in small projects. Data mistakes are often impossible to undo.

    Also in 3 projects that use this

  • SauravSrivastavSkill

    debug-failure

    Diagnose a failing test, command, or runtime behavior using evidence and produce a minimal verified fix.

    Also in 3 projects that use this

  • ficaviolaodorata520Skill

    security-pass

    Review an MCP server for common security gaps: LLM-facing surfaces as injection vector (tools, resources, prompts, descriptions), scope blast radius, destructive ops without consent, upstream auth shape, input sinks (URL / path / roots / shell / sampling / schema strictness / ReDoS), tenant isolation, leakage through errors and telemetry, unbounded resources, and HTTP-mode deployment surface. Use before a release, after a batch of handler changes, or when the user asks for a security review, audit, or hardening pass. Produces grouped findings and a numbered options list.

    Also in 3 projects that use this

  • Codagent-AISkill

    implement-change

    Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.

    Also in 5 projects that use this

  • +6 more from yaohuangguan

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the knowledge graph to plan and execute refactoring with confidence.

    line 8
  2. Very specific:

    Use refactor_tool with mode="suggest" for community-driven refactoring suggestions.

    line 12
  3. Very specific:

    Use refactor_tool with mode="dead_code" to find unreferenced code.

    line 13
  4. Very specific:

    Use apply_refactor_tool with the refactor_id to apply renames.

    line 15
  5. Very specific:

    After changes, run detect_changes_tool to verify the refactoring impact.

    line 16
  6. Distinctive:

    Always preview before applying (rename mode gives you an edit list).

    line 20
  7. Very specific:

    Check get_impact_radius_tool before major refactors.

    line 21
  8. Very specific:

    Use get_affected_flows_tool to ensure no critical paths are broken.

    line 22
  9. Very specific:

    Run find_large_functions to identify decomposition targets.

    line 23
  10. Very specific:

    ALWAYS start with get_minimal_context(task="<your task>") before any other graph tool.

    line 26
  11. Very specific:

    Use detail_level="minimal" on all calls.

    line 27

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

Use the knowledge graph to plan and execute refactoring with confidence.

Steps

  1. Use refactor_tool with mode="suggest" for community-driven refactoring suggestions.
  2. Use refactor_tool with mode="dead_code" to find unreferenced code.
  3. For renames, use refactor_tool with mode="rename" to preview all affected locations.
  4. Use apply_refactor_tool with the refactor_id to apply renames.
  5. After changes, run detect_changes_tool to verify the refactoring impact.

Safety Checks

  • Always preview before applying (rename mode gives you an edit list).
  • Check get_impact_radius_tool before major refactors.
  • Use get_affected_flows_tool to ensure no critical paths are broken.
  • Run find_large_functions to identify decomposition targets.

Token Efficiency Rules

  • ALWAYS start with get_minimal_context(task="<your task>") before any other graph tool.
  • Use detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.
  • Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.

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