What problem does it solve? Writing consistent, well-formatted commit messages is tedious and often skipped, leading to unclear git history. This Skill analyzes your working tree changes and produces a properly formatted conventional commit message, without ever touching git state. ## Core Features & Use Cases - Read-Only Git Analysis: Inspects staged and unstaged changes via git status and git diff, with strict safety rules that prohibit any commit, push, or history modification. - Plan-Aware Context: Detects plan files among changed files and uses them as the primary basis for the message, cross-referencing intent against actual code changes. - Conventional Commits Formatting: Applies correct type, scope, imperative description, body, and breaking-change footers, including dependency bump formatting. - Use Case: After finishing a feature across backend and domain packages, ask for a commit message and receive something like feat(backend,domain): add quota model and API with a body summarizing the plan deliverables. ## Quick Start Review my current uncommitted changes and write a conventional commit message for them.
