Generate structured commit messages with What/Why/How sections from staged diffs.
npx skills add https://github.com/Hyd3-14/dotfiles --skill commit-with-why
Please help me install this Agent Skill. Skill: commit-with-why Source: https://github.com/Hyd3-14/dotfiles/tree/main/home/.agents/skills/commit-with-why Command: npx skills add https://github.com/Hyd3-14/dotfiles --skill commit-with-why
This skill reduces cognitive load when crafting meaningful commits by automatically generating a clear subject and What/Why/How sections from the staged changes.
Provide the staged diff and a brief change purpose, then invoke the commit-with-why skill to generate the commit message.
High-intent search queries and answers about installing and using this skill.
You can auto-generate structured commit messages by providing the staged diff and a brief change purpose to produce a Subject line and What/Why/How bullet points. The tool extracts scope from the diff to ensure consistent message formatting.
Using a structured What/Why/How commit message format is the best way to explain why changes were made. This approach separates change descriptions from justifications, guarding against scope creep and reducing cognitive load during code reviews.
Yes, this commit message generator supports multiple file changes within a single staged diff. It processes the entire diff to extract the overall scope and generates a unified message with optional How guidance for non-obvious steps across all modified files.
Yes, you can use this tool for ambiguous code changes by providing a brief change purpose alongside the staged diff. The tool processes the diff scope and your context to populate the What and Why sections, clarifying intent for complex updates.
You should not use automated commit message generation when your staged changes contain sensitive data, as the tool explicitly avoids exposing sensitive information. Manual review remains recommended for commits requiring strict security compliance or custom formatting.
Nathan13888Summarize current git branch commits and diffs relative to trunk.
mattg101Stage all changes, commit with a message, and push to a remote Git repository.
helderbertoStage all Git changes, generate a commit message, and push to the current branch.
jonmagicGenerate conventional-commit messages from staged changes with optional scope and body.
