agentleFS
netanelavrnetanelavr/dotcursor/skills/kit-strip-diff/SKILL.md

kit-strip-diff

Skill6 starsChanged 27 days agoMITView on GitHub

Remove extras from a finished diff. Use when the outcome already works and the diff still has unused additions, extra instruction lines, format-only hunks, or rare-case handling the outcome does not need.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Not choosing a smaller path before coding (kit-minimize)

    line 13
  2. Very specific:

    Not proving the change works (kit-prove)

    line 14
  3. Very specific:

    Not a bug or design review (kit-review)

    line 15
  4. Very specific:

    Not checking what else the change could break (kit-check-blast)

    line 16
  5. Very specific:

    Not a token audit of what loads before the user types (kit-optimize-context)

    line 17
  6. Distinctive:

    Not moving working logic from a shared file to the one caller

    line 18
  7. Very specific:

    Not the always-on habit while typing (kit-keep-diff)

    line 19
  8. Distinctive:

    Default: uncommitted changes, staged and unstaged.

    line 23
  9. Distinctive:

    Read the outcome and the surrounding code.

    line 27
  10. Distinctive:

    Leave a change the outcome needs, even when it looks large.

    line 34
  11. Distinctive:

    Stop. Wait for all, a subset, or no.

    line 40
  12. Distinctive:

    Check result, or that you could not run one

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Strip diff

The outcome already works. Cut what this diff does not need. Ask before you delete or restore anything.

What this is NOT

  • Not choosing a smaller path before coding (kit-minimize)
  • Not proving the change works (kit-prove)
  • Not a bug or design review (kit-review)
  • Not checking what else the change could break (kit-check-blast)
  • Not a token audit of what loads before the user types (kit-optimize-context)
  • Not moving working logic from a shared file to the one caller
  • Not the always-on habit while typing (kit-keep-diff)

Scope

Default: uncommitted changes, staged and unstaged. If they name a branch, a commit range, or a path, use that. If the boundary is unclear, ask once.

What to cut

Read the outcome and the surrounding code. Flag a hunk only when you can show it is extra.

  1. Unused addition. A symbol, type, or file this diff added that nothing calls. Deleting it leaves behavior the same.
  2. Extra instruction. A new or edited line in a skill, rule, or agent doc that repeats a line already there, or that a competent model would do without being told. Cut that line only.
  3. Format-only hunk. Order, wrap, or whitespace changed, and the meaning matches the base version. Restore the base text. If you cannot show the match, leave the hunk.
  4. Rare case. A branch or helper this diff added for a case the agreed outcome does not need. Deleting it leaves that outcome the same.

Leave a change the outcome needs, even when it looks large. A clean hunk gets no finding.

Flow

  1. State the scope in one line.
  2. List findings: file, what is extra, which of the four kinds, and the cut.
  3. Stop. Wait for all, a subset, or no.
  4. Apply only the approved cuts. Do not rewrite working behavior.
  5. Re-run the check the repo already uses for the files you touched. If it fails, undo that cut.

Hand back

  • What you removed, by kind
  • Lines removed and added
  • Check result, or that you could not run one

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.