agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/minimal-diff/SKILL.md

minimal-diff

Skill1 starsChanged 41 days agoMITView on GitHub

Keep changes as small and focused as possible. Use when implementing features, fixing bugs, or refactoring alongside other work.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not reformat unrelated code.

    line 15
  2. Distinctive:

    Do not rename or move files unless required.

    line 16
  3. Distinctive:

    Do not add abstractions for one-time use.

    line 17
  4. Distinctive:

    Do not expand scope into cleanup, drive-bys, or “while I’m here.”

    line 18
  5. Distinctive:

    Prefer editing existing functions over adding parallel ones.

    line 20
  6. Distinctive:

    Delete dead code only when it blocks or is caused by this change.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Minimal Diff

Goal

Ship the smallest change that correctly solves the stated problem.

Rules

  • Touch only files required for the task.
  • Do not reformat unrelated code.
  • Do not rename or move files unless required.
  • Do not add abstractions for one-time use.
  • Do not expand scope into cleanup, drive-bys, or “while I’m here.”
  • Match existing style, naming, and structure exactly.
  • Prefer editing existing functions over adding parallel ones.
  • Delete dead code only when it blocks or is caused by this change.

Checklist

  • Diff matches the request and nothing else
  • No unrelated whitespace or import churn
  • No new dependencies unless necessary
  • Tests cover the changed behavior only

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