Generate WHY-focused commit messages for staged changes with testing and linting checks.
npx skills add https://github.com/atusy/dotfiles --skill git-commit-atusy
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/atusy/dotfiles/tree/main/dot_claude/skills/git-commit Command: npx skills add https://github.com/atusy/dotfiles --skill git-commit-atusy
This skill helps developers stage meaningful changes and craft commits that explain the rationale behind each change, improving traceability and code review quality.
Use the /git:commit slash command to commit staged changes with an explicit WHY.
High-intent search queries and answers about installing and using this skill.
WHY-focused git commit messages state the purpose and impact of staged changes rather than just the what. They improve traceability and code review quality by conveying the developer's intent behind each modification.
The best way to automate disciplined git commits for code reviews is to enforce a checklist requiring tests and linting to pass before committing, while deriving context-rich messages from the change details and rationale.
To commit staged changes as a single logical unit in version control, apply a discipline checklist that groups related modifications, requires passing tests and linting, and generates a concise WHY-focused message for the specific change.
Yes, this git workflow requires tests and linting to pass before committing. It enforces a discipline checklist that ensures staged code changes meet quality standards and represent a single logical unit before generating a commit message.
You need WHY-focused commit messages in your version control workflow during daily code changes, feature work, bug fixes, and code reviews, where commit messages must clearly convey the intent and rationale behind each modification.
Yes, you can use this commit approach for both individual developers and teams. It applies to daily code changes and code reviews, ensuring commits reflect a single logical unit with context-rich WHY-focused messages for everyone.
Neko-ProtocolReview staged changes and generate Conventional Commits messages.
bketelsenGenerate Conventional Commits with memory context and secret guards.
mbtzExecute a Git checklist to stage, commit, and push code changes.
ivyStage intended files and write conventional, why-focused commit messages.
