crafting-commits

Conventional commits standardize commit history with a structured format: type(scope): description. This Skill automatically drafts compliant messages for fixes, features, refactors, and breaking changes, validating structure and adding co-author attribution to enforce consistency across your project.

Yes. This Skill handles simple commits like fix and docs, complex ones like feat and refactor, and breaking changes requiring approval. Provide a short description of your change and it drafts the full message with type, scope, body, and migration guidance as needed.

Co-Authored-By lines credit collaborators in commit messages. This Skill formats and appends them automatically when you specify contributors, ensuring proper git and GitHub recognition without manual formatting.

The Skill validates conventional-commit structure, enforces correct type and scope, checks message body content, integrates with git status and diff, runs pre-commit style checks, and guides quality standards to prevent malformed commits from entering history.

Basic familiarity with git and command-line workflows helps, but the Skill handles the technical formatting. You provide change descriptions; it generates the structured message, reducing the knowledge barrier for consistent commits.

Level 1 (simple) covers fix, docs, style, chore. Level 2 (complex) includes feat, refactor, perf with larger scope. Level 3 (breaking) signals incompatible changes requiring explicit approval. This Skill applies the right structure and validation for each level.