What problem does it solve? Writing consistent, well-formatted git commit messages is easy to get wrong: vague subjects, missing context, accidentally staged secrets, and inconsistent conventions. This Skill standardizes the entire commit workflow so every commit follows conventional commit formatting with proper staging hygiene and co-author attribution. ## Core Features & Use Cases - Conventional Commit Formatting: Enforces type prefixes (feat, fix, refactor, docs, style, test, chore), imperative mood subjects under 50 characters, and body wrapping at 72 characters. - Smart Staging Guidance: Stages specific files or directories while avoiding git add . to prevent committing secrets, node_modules, or build artifacts. - Co-Author Attribution: Automatically appends the Co-Authored-By trailer to every commit message. - Use Case: After implementing a new API controller across several files, use this Skill to review the diff, stage only the relevant source files, run pre-commit checks (type check, lint, tests), and produce a verified conventional commit. ## Quick Start Ask the agent to commit the current changes using the commit skill with a conventional commit message and co-author tag.