agentleFS
Sign inStart free
YassimbaYassimba/loom/skills/refactor/SKILL.md

refactor

Skill9 starsChanged 2 months agoApache-2.0View on GitHub

Strict refactor review with visual before/after proposals and verified implementation.

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

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

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 3

    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 project instructions, the changed implementation, relevant callers, and test, and for broad or multi-subsystem changes, use subagents

    line 13
  2. Distinctive:

    Use all appropriate diagram types to present the change and add before and after codesnippet.

    line 25
  3. Distinctive:

    Ask for approval to implement the proposals.

    line 37

“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

1. Inspect

Review the user's scope. Otherwise review the current uncommited changes, including dirty and untracked source. Exclude generated, vendored, and build output.

Read project instructions, the changed implementation, relevant callers, and test, and for broad or multi-subsystem changes, use subagents

Send out subagent per topic:

  • general simplification: NUCLEAR
  • dependencies or custom machinery: OSS
  • recurring abstractions or indirection: patterns
  • changed or repetitive tests: tests
  • casts, optional state, or weak invariants: types

Present the proposed refactor(s) directly in chat. Use fenced mermaid blocks so the built-in renderer displays them.There is support for flowchart, ER, class diagrams, gitgraph, mindmap, pie, sequence , state and timeline.

Use all appropriate diagram types to present the change and add before and after codesnippet. Mark before and after explicitely.

In the diagram use these classes:

  • :::red removed
  • :::green added
  • :::orange changed

To mark changes, DON'T add your own color, keep background transparent, these classes already get colored automatically by the rendered.

4. Apply

Ask for approval to implement the proposals.

Task / scope: $ARGUMENTS

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