git-commit_skill

Overview

This skill guides creating well-structured git commits with clear, actionable commit messages and proper attribution. It walks through inspecting repository state, drafting a concise message, staging exact files, performing a signed commit, and verifying success. The skill enforces safety checks for secrets and pre-commit hook handling.

How this skill works

It inspects the working tree and index using git status and git diff, reviews recent commits for style consistency, and analyzes the nature, scope, and purpose of changes. It helps draft an imperative, under-72-character subject line and a brief body focused on why the change was made. It stages named files, creates a commit with --signoff and an Assisted-by: trailer, then verifies the commit succeeded with git status.

When to use it

• You ask to commit changes, create a commit, or stage and commit files.
• You request a suggested commit message or want help drafting one.
• You want commits to follow a specific style and include attribution.
• You need a safety check for secrets or pre-commit hook failures.
• You want to stage only specific files rather than adding everything.

Best practices

• Inspect git status and both staged and unstaged diffs before committing.
• Describe the purpose (why) in the commit message; use imperative verbs for the subject.
• Keep the subject under 72 characters and body to 1–2 short sentences for simple changes.
• Stage specific file paths (git add path/to/file) instead of using git add . or -A.
• Always use --signoff and include an Assisted-by: trailer in the commit message.
• Check for secrets (.env, private keys) and do not commit them; warn the user if detected.

Example use cases

• User: 'Commit my changes' — run status/diffs, draft message, stage files, commit with sign-off, confirm success.
• User: 'Write commit message' — analyze changes and suggest an imperative, concise subject and optional body.
• User: 'Stage and commit only tests' — identify test files, stage specific paths, create a signed commit.
• User: 'I got a pre-commit failure' — explain that the commit did not happen, fix issues, re-stage, and create a new commit.
• User: 'Ensure no secrets are committed' — scan diffs for suspicious files and block or warn before staging.