git-commit_skill

Overview

This skill executes git commits using Conventional Commits with intelligent analysis and staging. It inspects diffs to auto-detect type and scope, generates a concise conventional commit message, and can interactively stage files or accept overrides. It enforces safe Git practices to avoid secrets and destructive operations.

How this skill works

The skill analyzes the current repository state (staged diff first, then working tree diff) and the git status to determine changed files and logical groupings. It infers commit type, scope, and a present-tense, imperative description from the diff, suggests a message, and can auto-stage files or prompt for interactive staging and overrides. Finally it runs git commit with the generated or user-edited message, respecting hooks and safety rules.

When to use it

• When you want a conventional commit created from your workspace changes
• When you type or mention "/commit" or ask to commit changes
• When you need intelligent staging to group related files into one commit
• When you want an autogenerated commit message based on the actual diff
• When you want interactive control over type, scope, or description

Best practices

• Keep one logical change per commit and stage accordingly
• Use present-tense, imperative descriptions under 72 characters
• Verify no secrets (.env, keys, credentials) are included before committing
• Prefer adding references (Closes #123) or BREAKING CHANGE footers when needed
• Do not bypass hooks (--no-verify) or run destructive commands unless explicitly requested

Example use cases

• Auto-generate a feat: message after adding a new API endpoint and stage the related files together
• Create a fix: commit from a small bug fix found in a single file, with concise scope inferred
• Interactively stage tests and source changes and customize the commit scope and description
• Group multiple styling and refactor changes into separate commits by intelligent file selection
• Add a breaking change footer when a public API was modified and include the BREAKING CHANGE note