commit
Skill5 starsChanged 52 days agoMITView on GitHub
Write a commit message for the staged change. Follows the subject convention the repo's history or instruction files set, and otherwise writes an imperative subject under 72 characters with a body that says only what the diff cannot show. Writes the message only, unless the user asks to commit.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- ShipfoxHQ/shipfoxtheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
Used with
Projects with it also use act-on-feedback, generate-run-commands 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.
MicrosoftSkillact-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Also in 4 projects that use this
MicrosoftSkillgenerate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
Also in 4 projects that use this
shawn-dumasSkillvalidate-plan
Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.
Also in 5 projects that use this
MindgamesSkillbranch
Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.
Also in 9 projects that use this
decocmsSkilladd-mcp-tools
Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration
Also in 3 projects that use this
mitsuhikoSkilloebb-scotty
Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.
Also in 3 projects that use this
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- microsoft/vscode★ 195ksame name
- TryGhost/Ghost★ 56ksame name
- ToolJet/ToolJet★ 41ksame name
- ShareX/ShareX★ 41ksame name
- openai/symphony★ 27ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- windmill-labs/windmill★ 19ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
177 more not listed
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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- prSkill
- review-replySkill
- rules-checkSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
When git diff --cached --no-relative --quiet exits 0, nothing is staged.
- Distinctive: line 45
When git status --porcelain also shows unstaged or untracked changes, leave them out of the message and tell the user they are not in it.
- Distinctive: line 52
When none of those gives a reason, write none: a motive you inferred from the diff is a guess.
- Very specific: line 70
Read ${CLAUDE_SKILL_DIR}/../pr/conventions.md and run its lookup for one destination: the commit message.
- Very specific: line 81
When a source covers the subject, match it.
- Distinctive: line 86
When the convention uses a ticket key, the key comes only from what the user typed, the branch name, or the issue step 1 read.
- Distinctive: line 87
When none of those names one, leave the key out and say so in the reply.
- Distinctive: line 96
When a source covers the body, follow it, and follow the default for whatever the source does not say, such as a rule that asks only for a …
- Distinctive: line 103
When every sentence fails that test, the commit has no body: the message is the subject alone.
- Very specific: line 108
Add a trailer only when the convention requires one, such as a ticket key or Signed-off-by:.
- Very specific: line 122
Write the message to a file from mktemp, never in the work tree, so it never lands in a later git add.
- Very specific: line 128
Commit only when what the user typed asks for it, such as /katharsis:commit and commit it.
“Common” is measured: kept by at least 6 in 10 of the 167 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.
Files
Katharsis commit message
You write the commit message for the change staged in the current repo. The reader runs
git log months from now with the diff beside the message and without this session, so the
message spends its words on what the diff cannot show.
What the user typed after the command, empty when they typed nothing:
$ARGUMENTSIt may say why the change was made, or ask for something more, such as committing it. Do only what it asks. When it asks for nothing beyond the message, write the message and stop: commit nothing.
1. Gather the change
The message covers the staged change only. Read it:
git diff --cached --no-relative --stat
git diff --cached --no-relative
git write-tree--no-relative keeps a diff.relative setting from hiding staged files outside the current
folder, which git commit still commits. Pass it to every git diff here.
git write-tree prints the hash of the index's tree. Keep it: step 6 compares it before any
commit. When it fails, such as when the index has unmerged paths, write no message: show its
error, say the conflict must be resolved first, and stop.
When git diff --cached --no-relative --quiet exits 0, nothing is staged. Write no message: show
the user git status --short, say that nothing is staged and that the skill stages nothing, and
stop. Never stage files to have something to describe.
When git status --porcelain also shows unstaged or untracked changes, leave them out of the
message and tell the user they are not in it.
Find why the change was made. The diff shows what changed; the reason comes from what the user
typed after the command, this session's conversation, or an issue that a #123 or ticket key in
the branch name or in what the user typed points to, read with gh issue view when gh can reach
it.
When none of those gives a reason, write none: a motive you inferred from the diff is a guess.
2. Find the convention
Resolve the comparison ref for the history, the default branch, from the first of these that gives one:
git symbolic-ref --short refs/remotes/origin/HEAD, such asorigin/main.- The remote's default branch from
git ls-remote --symref origin HEAD, whoseref: refs/heads/mainline namesmain, read asorigin/mainwhen that ref exists. origin/mainororigin/master, whichever exists.- The local
mainormaster, whichever exists. HEAD, the checked-out branch's own history.
A command that fails, such as exiting 128 with fatal: in a repo with no remote, or prints
nothing, gives no ref. Check that a ref exists with git rev-parse --verify --quiet <ref>. When
the repo has no commits yet, the history covers nothing.
Read ${CLAUDE_SKILL_DIR}/../pr/conventions.md and run its lookup for one destination: the
commit message. Look up its subject and its body on their own, the way /katharsis:pr looks up
the title and the body, and stop at the first source that covers each. A source can cover one part
and say nothing about the other, such as a CONTRIBUTING.md that says "explain why in the body"
or "sign off every commit" and names no subject format; then that part follows the source, and the
lookup goes on to the later sources for the other part. A part no source covers follows the
default. A history whose commits all have empty bodies does not cover the body, since an empty
body is an absence rather than a rule.
3. Write the subject
When a source covers the subject, match it. A history whose subjects mostly start with a
type(scope): prefix, a ticket key, or an [area] tag gets the same form, with the type and
scope chosen from the ones the history already uses for this kind of change and this part of the
repo. A rule that names its own form, length, or mood wins over the history.
When the convention uses a ticket key, the key comes only from what the user typed, the branch name, or the issue step 1 read. When none of those names one, leave the key out and say so in the reply. Never copy a key from another commit.
Where the convention says nothing, the subject is in the imperative mood, under 72 characters including any prefix, with no trailing period, and names the effect rather than the edit: "Stop the parser dropping the last line", not "Update parser.py".
4. Write the body
When a source covers the body, follow it, and follow the default for whatever the source does not
say, such as a rule that asks only for a sign-off. The default body says only what the diff cannot
show: what users or callers hit before the change, as the reason sources in step 1 tell it, such as the failure or its cost, rather than
the old code, which git show already shows; why that was wrong; and why this fix rather than the
obvious alternative. Test every sentence: if the reader could recover it by running git show,
cut it. Never list the changed files, count lines, or narrate the order of the edits.
When every sentence fails that test, the commit has no body: the message is the subject alone.
A body is separated from the subject by one blank line, is written in complete sentences, and wraps at 72 characters.
Add a trailer only when the convention requires one, such as a ticket key or Signed-off-by:.
A Signed-off-by: trailer takes its name and email from git config user.name and
git config user.email. Never add a Co-Authored-By: trailer.
5. Check before showing
- No reference codes. The message holds no code this chat defined, such as
F3,AT2,NA2, orQ1. Write what the item says in its place. The reader ofgit lognever saw this chat. - Every claim traces to the change. Each behavior the message names is in the staged diff, and each reason comes from the sources step 1 names.
6. Hand it over
Write the message to a file from mktemp, never in the work tree, so it never lands in a later
git add. Show the message in the reply in one fenced text block, then the file's path and
one line of your own naming the source each part followed, such as "Subject follows the
history's fix(scope): prefix; body follows the default", or saying that none covered it and you
used the default.
Commit only when what the user typed asks for it, such as /katharsis:commit and commit it.
First run git write-tree again; when its hash differs from the one step 1 recorded, the staged
change moved under the message, so commit nothing and say so. Otherwise commit what is staged
with the file:
git commit -F <message file>Stage nothing: never git add, and never git add -A or git add .. Never pass --amend,
--no-verify, or --allow-empty, and never push. When the commit fails, such as when a
pre-commit hook rejects it, show the hook's output and the message file's path, and stop. When it
succeeds, remove the message file and report git log -1 --format='%h %s'; the reply then says the file was removed and gives no path.
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
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.

