What problem does it solve?
Developers often write terse or inconsistent commit messages that lack context, making code review, changelogs, and future debugging harder. This Skill guides the author to capture the purpose (Why) and the concrete changes (How) so each commit is informative and standardized.
Core Features & Use Cases
- Guided prompts to capture commit type, scope, short description, and the reasons for the change.
- Automated analysis of git diffs to synthesize concrete How points from staged changes without asking the user to restate low-level details.
- Confirmation workflow that shows the generated message formatted with Why and How sections and optionally executes the commit, useful for maintainers and teams enforcing descriptive commit policies.
Quick Start
Use the skill to generate a Why/How formatted commit message from the current repository changes and confirm to run the commit.