commit
Skill245 starsChanged 9 months agoMITView on GitHub
Create standardized git commits following Terrae's conventions
- Reads credentials
187 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- gtapps/claude-code-hermittheir own version, first seen Nov 13, 2026
Used with
Projects with it also use validate-plan, act-on-feedback 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.
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
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 3 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
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 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
mitsuhikoSkillpi-share
Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.
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.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Create standardized git commits following Terrae's conventions.
- Distinctive: line 14
Run git status to see changed files
- Distinctive: line 15
Run git diff to see the actual changes
- Distinctive: line 20
Ask the user if they want to proceed with the commit
- Distinctive: line 24
Never stage sensitive files (.env, credentials, etc.)
- Distinctive: line 49
When committing a new component, split into 3 separate commits in this order:
- Very specific: line 57
Do NOT add Co-Authored-By lines
- Distinctive: line 58
Do NOT commit until user approves
- Very specific: line 59
Do NOT use --amend unless explicitly requested
- Distinctive: line 60
Do NOT push unless explicitly requested
- Distinctive: line 61
Keep commit messages concise (under 72 characters)
- Distinctive: line 70
Run git status to confirm commit succeeded
“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
Commit Skill
Create standardized git commits following Terrae's conventions.
Instructions
- Check Current State
- Run
git statusto see changed files - Run
git diffto see the actual changes
- Run
- Review Changes with User
- Summarize what files were changed
- Explain the nature of changes (new feature, bug fix, refactor, etc.)
- Ask the user if they want to proceed with the commit
- Stage Files
- Stage specific files by name (avoid
git add -Aorgit add .) - Never stage sensitive files (.env, credentials, etc.)
- Stage specific files by name (avoid
Commit Message Format Follow conventional commits:
type(scope): descriptionTypes:
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Formatting, no code changerefactor: Code restructuringtest: Adding or updating testschore: Maintenance tasks
Examples:
feat(marker): add rotation supportfix(popup): prevent memory leak on unmountdocs(readme): update installation instructions
New Component Convention
When committing a new component, split into 3 separate commits in this order:
feat(map): add {component} component— the source file (src/registry/map/{slug}.tsx)feat(docs): add {component} example components— all example files (src/app/docs/_components/examples/{slug}-*.tsx)feat(docs): add {component} documentation page— the docs page (src/app/docs/{slug}/page.tsx)
Shared file modifications (sidebar, components page, changelog, registry.json, barrel export) should be committed separately since they often contain changes for multiple components.
- Important Rules
- Do NOT add
Co-Authored-Bylines - Do NOT commit until user approves
- Do NOT use
--amendunless explicitly requested - Do NOT push unless explicitly requested
- Keep commit messages concise (under 72 characters)
- Do NOT add
Create the Commit
git commit -m "type(scope): description"- Verify
- Run
git statusto confirm commit succeeded - Show the commit hash to the user
- Run
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.

