Review staged Git changes and generate standardized commit messages.
npx skills add https://github.com/vm-wylbur/pb-dotfiles --skill commit-vm-wylbur
Please help me install this Agent Skill. Skill: commit Source: https://github.com/vm-wylbur/pb-dotfiles/tree/main/ai/claude-code/skills/commit Command: npx skills add https://github.com/vm-wylbur/pb-dotfiles --skill commit-vm-wylbur
Inconsistent Git commit messages, inclusion of debug code, or unapproved changes can degrade codebase quality, hinder collaboration, and make project history difficult to navigate. This skill enforces best practices for every commit, saving you review time and ensuring a clean history.
Pre-Commit Review: Automatically checks git status and git diff --cached to ensure only intended changes are staged, flagging issues like debug code, commented-out sections, or hardcoded secrets.
Standardized Message Generation: Drafts commit messages following a mandatory format (imperative mood, concise title, detailed body, specific "By PB & Claude" attribution), ensuring clarity and consistency.
User Approval Workflow: Presents the drafted message and staged changes for explicit user approval before executing the commit, giving you final control and preventing unintended commits.
Use Case: After making changes, when you say "commit", the skill will show you all staged changes, draft a commit message like "Add JWT authentication to API endpoints
Implemented token refresh
Updated expiry
By PB & Claude", and ask for your approval before finalizing the commit.
Commit the current changes. The skill will review staged files, draft a commit message, and ask for approval.
High-intent search queries and answers about installing and using this skill.
Standardized commit messages enforce consistent formatting—imperative mood, concise titles, detailed bodies—across all commits. This skill automatically drafts messages following a mandatory format and requires approval before committing, ensuring every commit adheres to your team's standards and improves project history readability.
Yes. This skill reviews all staged changes via `git status` and `git diff --cached` before committing, automatically flagging debug code, commented-out sections, and hardcoded secrets. It presents these issues for your review and approval, preventing unintended commits that degrade code quality.
A pre-commit review workflow checks exactly what you've staged, shows you all staged changes, and requires explicit approval before the commit executes. This skill implements that workflow automatically, giving you final control and preventing commits with unintended or problematic code.
Automating commit validation enforces best practices at commit time rather than during review. This skill checks staged changes, drafts standardized messages, and requires approval—catching issues early, reducing review time, maintaining a clean history, and ensuring consistent collaboration standards.
No. This skill generates commit messages automatically based on your staged changes, following mandatory format rules. You review and approve the drafted message before committing, eliminating repetitive manual writing while maintaining control and consistency.
Yes. This skill integrates into standard Git workflows by intercepting the commit step—it checks `git status`, reviews staged changes, drafts messages, and handles the actual commit. It fits any version control setup that uses Git and requires no additional configuration or dependencies.
BSteffaniakGenerate Git commit messages from staged changes and write them for commit tools.
biwakonbuPush the current Git branch to the remote with safety checks.
AmidVoshakulAutomate Git hook configuration for linting, formatting, and commit message validation.
notqueAutomate phase-gated git commit workflows with validation, staging, and CLAUDE.md compliance.
