git-commit-creator
Skill519 starsChanged 12 months agoApache-2.0View on GitHub
Creates properly formatted Git commits following conventional commit standards for the MCPSpy project. Use when asked to commit changes, stage files, or manage git workflows. Has access to git status, diff, checkout, add, and commit commands.
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- github-issue-creatorSkill
- go-testingSkill
- security-integration-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 29
Use standard prefixes: feat(component):, chore:, fix(component):
- Distinctive: line 32
Keep titles concise and descriptive
≈ “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
Git Commit Creator Skill
Automates the creation of well-structured Git commits for the MCPSpy project.
Workflow
You should STRICTLY follow the following steps:
- Understand the commit status through
git status,git diffandgit diff --staged. - Analyze the scope and nature of changes
- Using
git checkout -b <branch-name>, create concise branch name with standard prefixes (e.g.,feat,chore,fix). - Using
git commit -m "<commit-message>", create a conventional commit message that accurately reflects the changes.
Commit Message Convention
- Use standard prefixes:
feat(component):,chore:,fix(component): - Component examples:
library-manager,ebpf,mcp,http,output - Brackets are optional but recommended for clarity
- Keep titles concise and descriptive
Examples
feat(library-manager): add support for container runtime detectionchore: update dependencies to latest versionsfix(ebpf): handle kernel version compatibility issues
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.

