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.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
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." allowed-tools:
- 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
More by alex-ilgayev
View allCreates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels.
Handles all Golang testing tasks including running tests, writing new tests, and fixing test failures. Follows MCPSpy testing conventions with require for critical assertions and assert for non-critical ones.