git-commit-creator
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.
When & Why to Use This Skill
The Git Commit Creator skill automates the version control workflow by generating standardized, professional commit messages following conventional commit standards. It streamlines the entire Git process—from analyzing code diffs and staging files to creating descriptive branch names—ensuring a clean, searchable, and maintainable project history for developers and teams.
Use Cases
- Standardizing Project History: Automatically applying conventional commit prefixes like 'feat:', 'fix:', and 'chore:' to maintain a consistent and readable git log.
- Automated Workflow Management: Reducing manual overhead by allowing the AI to handle 'git add', 'git status', and 'git checkout' operations based on the current development context.
- Intelligent Change Analysis: Using 'git diff' analysis to generate accurate, concise descriptions of code changes without requiring the developer to manually summarize their work.
- Branch Organization: Creating structured branch names with standard prefixes to improve team collaboration and CI/CD pipeline integration.
| name | git-commit-creator |
|---|---|
| description | "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." |
| - Bash(git status | *) |
| - Bash(git diff | *) |
| - Bash(git diff-index | *) |
| - Bash(git add | *) |
| - Bash(git checkout | *) |
| - Bash(git commit | *) |
| - Bash(git show | *) |
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