GI

git-commit-creator

Ensures Git commits follow conventional standards for the MCPSpy project by analyzing changes and enforcing prefix conventions.

Install

mkdir -p .claude/skills/git-commit-creator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3143" && unzip -o skill.zip -d .claude/skills/git-commit-creator && rm skill.zip

Installs to .claude/skills/git-commit-creator

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
242 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Analyze git status and diffs
  • Create new branches with standard prefixes
  • Format commit messages to conventional standards
  • Stage changes for commit
  • Execute git commit commands

How it works

The skill inspects the current git state, prompts for branch creation using standard prefixes, and enforces conventional commit message formatting before executing git commands.

Inputs & outputs

You give it
Code changes and commit intent
You get back
Staged and committed git changes

When to use git-commit-creator

  • Staging and committing code changes
  • Creating new branches with standard prefixes
  • Formatting commit messages to conventional standards

About this skill

Git Commit Creator Skill

Automates the creation of well-structured Git commits for the MCPSpy project.

Workflow

You should STRICTLY follow the following steps:

  1. Understand the commit status through git status, git diff and git diff --staged.
  2. Analyze the scope and nature of changes
  3. Using git checkout -b <branch-name>, create concise branch name with standard prefixes (e.g., feat, chore, fix).
  4. 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 detection
  • chore: update dependencies to latest versions
  • fix(ebpf): handle kernel version compatibility issues

When not to use it

  • Committing changes outside the MCPSpy project
  • Bypassing conventional commit standards

Prerequisites

git installedMCPSpy project environment

Limitations

  • Strictly follows conventional commit standards
  • Requires clear identification of change scope

How it compares

It automates the enforcement of project-specific commit message conventions, ensuring consistency compared to manual git commits.

Compared to similar skills

git-commit-creator side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git-commit-creator (this skill)17moReviewBeginner
run-nx-generator53moReviewIntermediate
git-commit116moReviewBeginner
morph-search97moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry