commit_skill

Overview

This skill creates atomic conventional git commits following the Commitizen (cz) style and v1.0.0 specification. It inspects pending changes, performs safety checks, infers logical commit scopes, and produces validated commit messages that include required body bullets and a Co-Authored-By footer. The skill will request or update project-specific git settings when needed before committing.

How this skill works

The skill first verifies a project-level git configuration file and invokes a config workflow if that file is missing or incomplete. It scans staged and unstaged changes for sensitive files, large files, and oversized diffs, warning the user and requesting confirmation when issues are detected. The tool groups changes into coherent logical units, infers scopes, drafts Conventional Commit messages that satisfy title and body rules, validates them, stages the relevant files, and creates the commits including a Co-Authored-By footer.

When to use it

• Committing multiple related file changes that should be split into atomic commits
• Enforcing Conventional Commits style and Commitizen compatibility
• Preventing accidental commits of secrets, .env files, or extremely large files
• When project-specific commit scopes must be checked or updated before committing
• Automating commit message validation in CI or local workflows

Best practices

• Keep each commit focused on a single logical change to make review and revert easier
• Write title lines in all lowercase, imperative mood, under 50 characters with no trailing period
• Always include a body with at least one bullet line starting with an imperative verb
• Limit body lines to 72 characters and include context or explanation only where helpful
• Confirm or fix any detected secrets or very large files before proceeding

Example use cases

• Split a feature addition and related test updates into two atomic commits with proper scopes
• Enforce mandatory bullet-point bodies and Co-Authored-By attribution for team contributions
• Detect an accidentally staged .env file and prompt for removal before committing
• Auto-generate scope suggestions from changed file paths and update project config if needed
• Create multiple commits from a large working tree while warning on commits >500 lines