scope-commit
Skill2 starsChanged 19 days agoMITView on GitHub
Writes commit messages in Scoped Commits form: a `<scope>: <description>` subject and a body only for the why. Use before running any `git commit`, including `--amend` and a squash or fold, and for "write a commit", "commit message", "commit this" or /commit. MR/PR descriptions: use `scope-mr` instead.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-teamSkill
- assemble-metaSkill
- brainstormSkill
- build-issueSkill
- cut-milestonesSkill
- frictionSkill
- milestone-closeSkill
- qa-reviewSkill
- review-benchSkill
- scope-issueSkill
- scope-mrSkill
- scope-specSkill
- setup-dream-teamSkill
- ship-itSkill
- triage-issueSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Very specific: line 24
Never the kind of change: no feat:, feature:, chore:, perf:, style:.
- Distinctive: line 36
Write one only to carry a fact the diff cannot show: the original problem, why this approach, a known limit.
- Distinctive: line 40
Always a body: breaking changes, security fixes, data migrations.
- Distinctive: line 48
No work log: verification output, test counts, sweep tables.
- Distinctive: line 49
No review-facing content. That is the MR description.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Subject <scope>: <description>. Body = the why. Most commits don't need one.
subject
Shape
<scope>: <description>. Scope lowercase.- Imperative: "add", "fix", "remove". Never "added" / "adds" / "adding".
- ≤50 chars target. 72 hard cap.
- No trailing period.
Scope
- Names the area touched:
ansible:,preseed:,docs:,watchdog:. - Never the kind of change: no
feat:,feature:,chore:,perf:,style:. - Several areas → one broader scope. Else comma-separate.
- Tree-wide →
treewide:. - A project
CLAUDE.mdorAGENTS.mdscope vocabulary or stricter pattern wins. - An upstream repo's subject format, from its CONTRIBUTING or
git log, wins over the kind-of-change ban (fix(ntpq)!: …); the body rules still apply.
commit-style
When a body earns its place
- Default: no body.
- Write one only to carry a fact the diff cannot show: the original problem, why this approach, a known limit.
- Name that fact before you start. Can't name it → padding.
- Runs past one paragraph → padding.
- Always a body: breaking changes, security fixes, data migrations.
Content
- Cite, don't restate. Issues and decision records by number; records are where
<base directory>/../../references/repo-conventions.mdresolves. - A diff that is itself prose — docs, rules, comments, config — is cited the same way, never re-explained.
- No work log: verification output, test counts, sweep tables. CI's job.
- No review-facing content. That is the MR description.
Format
- ~80 words the shape. 160 hard cap. Length tracks rationale, not diff size.
- Wrap at 72 columns (
git logindents four; patches stay under RFC 2822's 78). - Bullets
-, never*. - Issue refs (
Closes #42) on their own line at the end.
body-issues
- Impersonal prose. No self-narration.
- No "I" / "we".
- No "now" / "currently".
- Wrapped at 72.
trailers
- One logical change, one commit: fold a follow-up fix into the commit it repairs before merge.
- Late change the user asks for on an open MR/PR →
git commit --amendthe commit it changes. - Reverts and merges keep Git's default format.
- A revert adds one line saying why.
Examples
❌ feat: added a new endpoint to get user profile information from the database
✅
api: add GET /users/:id/profile
Mobile needs profile data without the full user payload — cold-launch
on LTE was fetching 40 KB to render three fields.
Closes #128✅ subject-only, needs no body: spill: drop unused zstd level knob
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.

