agentleFS
Sign inStart free
eeshsaxenaeeshsaxena/agent-skills/skills/commit-surgeon/SKILL.md

commit-surgeon

Skill2 starsChanged 3 months agoMITView on GitHub

Turn a messy working tree into clean, atomic, conventional commits with sharp messages. Use before committing or when staged changes mix concerns.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ame589/Claude_skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    One concern per commit: If a change touches a feature and also fixes an unrelated typo, that is two commits.

    line 14
  2. Very specific:

    Use conventional prefixes: when the repo already does: feat:, fix:, refactor:, docs:, test:, chore:, perf:.

    line 19
  3. Distinctive:

    Run git status and git diff --staged (and git diff) to see everything.

    line 30
  4. Distinctive:

    Before finishing, run git log --oneline on your new commits and confirm each line reads clearly on its own.

    line 33
  5. Distinctive:

    Do not write "update", "fix stuff", "wip", or "misc" as a subject.

    line 48
  6. Distinctive:

    Do not add co-author or tooling trailers unless the human asks.

    line 49
  7. Distinctive:

    Do not amend or force-push shared history without explicit instruction.

    line 50

≈ “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

Commit Surgeon

Sloppy commits are technical debt in the git log. Your job is to split work into the smallest set of commits that each tell one coherent story, and to write messages a reviewer can trust without opening the diff.

Rules

  1. One concern per commit. If a change touches a feature and also fixes an unrelated typo, that is two commits. Use git add -p to stage by hunk.
  2. The subject line is a promise. Under 60 characters, imperative mood ("Add retry to upload", not "Added" or "Adds"). It should complete the sentence "If applied, this commit will ___".
  3. Use conventional prefixes when the repo already does: feat:, fix:, refactor:, docs:, test:, chore:, perf:. Match the repo's existing style over any personal preference. Check git log --oneline -20 first.
  4. The body explains why, not what. The diff already shows what changed. The body covers the reason, the trade-off, and anything a future reader would be surprised by. Wrap at 72 columns. Skip the body for trivial changes.
  5. Never bundle formatting churn with logic. Whitespace or import reordering goes in its own chore: commit so real changes stay readable in review.

Workflow

  1. Run git status and git diff --staged (and git diff) to see everything.
  2. Group the changes mentally into logical units.
  3. Stage and commit each unit separately with git add -p when needed.
  4. Before finishing, run git log --oneline on your new commits and confirm each line reads clearly on its own.

Message template

<type>: <imperative summary under 60 chars>

<why this change exists and what it trades off, wrapped at 72 cols>

<optional: refs, breaking-change notes, follow-ups>

Do not

  • Do not write "update", "fix stuff", "wip", or "misc" as a subject.
  • Do not add co-author or tooling trailers unless the human asks.
  • Do not amend or force-push shared history without explicit instruction.

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