commiter
Skill0 starsChanged 3 months agoMITView on GitHub
Create standardized commits and push current repository changes when the user explicitly requests a commit.
- Commits and pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Aiatulla/agent-kittheir own version, first seen Oct 17, 2026
- databricks-solutions/apxtheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- databricks-solutions/apx★ 91same name
- Aiatulla/agent-kit★ 2same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend-doc-syncSkill
- check-documentation-gapsSkill
- check-test-gapsSkill
- docs-guardianSkill
- monthly-doc-actualizerSkill
- release-note-writerSkill
- story-checkSkill
- story-guardianSkill
- story-updateSkill
- tech-debtSkill
- test-scenario-guardianSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill only when the user explicitly asks to create a commit.
- Very specific: line 13
Create a git commit with a single-line message in this exact format: username: date: Short description in one line
- Distinctive: line 17
Run only on direct user request to commit (examples: "commit", "create commit", "$commiter").
- Distinctive: line 18
Do not run automatically after code changes.
- Distinctive: line 28
Must fit one line.
- Distinctive: line 79
Never amend existing commits unless the user explicitly asks.
- Distinctive: line 80
Never use destructive git commands.
- Very specific: line 81
If pre-commit is configured, do not skip it.
≈ “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.
Files
Commiter (Repo Local Skill)
Use this skill only when the user explicitly asks to create a commit.
Scope boundary: this skill must not run make test. Project-specific testing belongs to the applicable testing skill.
Goal
Create a git commit with a single-line message in this exact format:
username: date: Short description in one line
Trigger Rules
- Run only on direct user request to commit (examples: "commit", "create commit", "$commiter").
- Do not run automatically after code changes.
- On explicit commit request, do not ask file-selection questions; commit all current working tree changes.
Commit Message Rules
username:- First choice:
git config user.name - Fallback:
whoami
- First choice:
date: useYYYY-MM-DDformat.Short description in one line:- Imperative, concise, no trailing period.
- Must fit one line.
Workflow
- Confirm there are staged or unstaged changes:
git status --short- Stage all current changes (tracked + untracked) without asking follow-up questions:
git add -A- Build commit message using required format.
- Pre-commit checks (required when configured):
- Detect whether pre-commit is configured:
.pre-commit-config.yamlexists, or.git/hooks/pre-commitexists.
- If configured, run:
pre-commit run --all-files- If checks fail:
- inspect errors and apply fixes in code/config (lint, formatting, imports, typing, etc.)
- re-run
pre-commit run --all-files - repeat until it passes or a real blocker is reached
- Re-stage any files changed by auto-fixes:
git add <files>4.5) If the current work mixes documentation cleanup with functional DB/API changes, prefer a separate commit boundary when practical. If the mix is intentional, note that in the final report and capture any deferred process concern in tech-debt/<YYYY-MM-DD>.md before committing.
- Commit:
git commit -m "<username>: <YYYY-MM-DD>: <short one-line description>"- Push current branch to default remote:
git push- Report:
- committed files
- final commit hash
- final commit message
- push result
Notes
- Never amend existing commits unless the user explicitly asks.
- Never use destructive git commands.
- If
pre-commitis configured, do not skip it.
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.