write-git-commit
Skill1.2k starsChanged 10 months agoMITView on GitHub
Create a git commit following repository conventions
Trending
Quiet since May.thin dataabout the whole repository
Who's talking about jamiebrynes7/obsidian-todoist-plugin
- Ledaryy/obsidian-todoist-completed-tasks“[Feature Request] Automatic task fetching”GitHub · Jan 15, 2023 · 2 reactions
- debuglevel/obsidian-tasks“Disable warnings about tasks in callouts”GitHub · May 29, 2026
- d-eniz/jupymd“fix: code blocks in pdf export”GitHub · Jan 16, 2026
- xhuajin/obsidian-tabs“[BUG] Certain Codeblocks Not Rendering Inside Tab”GitHub · Jul 27, 2024
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- plugin/CLAUDE.mdCLAUDE.md
- write-changelogSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 8
Create git commits following the repository's established conventions.
- Distinctive: line 34
Use lowercase after the colon
- Distinctive: line 35
Use imperative mood ("add feature" not "added feature")
- Distinctive: line 36
No period at the end
- Distinctive: line 37
Keep concise (ideally under 72 characters total)
- Distinctive: line 50
Use sparingly - only when the subject isn't self-explanatory
- Distinctive: line 61
DO NOT add Claude as a coauthor to the commit.
- Distinctive: line 65
Run git status to see staged and unstaged changes
- Distinctive: line 66
Run git diff --staged to review what will be committed
- Distinctive: line 69
Write a clear, concise subject line
- Distinctive: line 70
Add a body only if the "why" isn't obvious
≈ “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.
Files
Git Commit
Create git commits following the repository's established conventions.
Commit Message Format
<scope>: <subject>
[optional body]Scope
The scope indicates which part of the codebase is affected:
plugin- Plugin source code changes (most common)docs- Documentation changesscripts- Build/release script changes.github- GitHub workflows and actions.claude- Claude configuration and skills.vscode- VS Code settings*- Changes spanning multiple packages/areas
For focused changes within a scope, you may use a more specific prefix like plugin api, plugin settings, etc.
Subject Line
- Use lowercase after the colon
- Use imperative mood ("add feature" not "added feature")
- No period at the end
- Keep concise (ideally under 72 characters total)
Examples:
plugin: add support for task filteringdocs: update query-blocks documentation*: bump versions across the board.github: add separate build job
Body (Optional)
- Separate from subject with a blank line
- Explain why the change was made, not what
- Use sparingly - only when the subject isn't self-explanatory
Example:
plugin: restore react & react-dom dedupe
While the tests pass after aligning react versions between docs/ and
plugin/, the build still breaks at runtime without this.DO NOT add Claude as a coauthor to the commit.
Process
- Run
git statusto see staged and unstaged changes - Run
git diff --stagedto review what will be committed - Stage files with
git add <files>(prefer specific files overgit add -A) - Determine the appropriate scope based on changed files
- Write a clear, concise subject line
- Add a body only if the "why" isn't obvious
- Create the commit
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.

