mcpField
C
commit

commit

github.com/derogabDevelopment4363 installsUpdated 6d ago
Repository

About commit

A skill that creates one Git commit from staged changes only. It checks that changes are staged and guides Conventional Commits formatting, without staging files or pushing to a remote.

Key features

  1. 01Commit staged changes only
  2. 02Check for staged changes first
  3. 03Use Conventional Commits format
  4. 04Match recent commit style
  5. 05Never stage or push changes

Use cases

  1. 01Commit prepared code changes
  2. 02Write a consistent commit message
  3. 03Avoid committing unstaged files

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/derogab/agent-kit --skill commit

After installing, type/commitin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Context

  • Staged diff: !git diff --staged
  • Branch: !git branch --show-current
  • Recent commits: !git log --oneline -5

Your task

Create a single git commit from the staged changes only.

Pre-flight checks
  1. If there are no staged changes, stop immediately and tell the user to stage files first. Do nothing else.
  2. Never run git add. Never run git push. Only commit what is already staged.
Commit message format

Follow Conventional Commits (https://www.conventionalcommits.org/en/v1.0.0/):

<type>(<optional scope>): <description>

[optional body]

Types:

  • feat – new capability
  • fix – bug fix
  • docs – documentation only
  • refactor – restructuring without functional change
  • test – test creation or modification
  • chore – routine maintenance (including dependencies)
  • build – build system or external dependencies
  • perf – performance improvement
  • ci – CI/CD changes

Append ! after the type/scope for breaking changes (e.g. feat!: change API response format).

Rules
  • Infer the correct type from the diff.
  • Write a concise description (lowercase, imperative mood, no period).
  • Add a body only when the diff is non-trivial and the "why" isn't obvious from the description.
  • Body: wrap at 72 characters, explain why not what.
  • Match the style and tone of the recent commits shown above.
  • Use a HEREDOC to pass the message to git commit -F -.
  • Do not send any text besides the tool calls.

Comments

Markdown supported