commit-with-validation

Create atomic Git commits with standardized messages and pre-commit validation.

7|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/BerryKuipers/claude-code-toolkit --skill commit-with-validation
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: commit-with-validation
Source: https://github.com/BerryKuipers/claude-code-toolkit/tree/main/.claude/skills/git-workflows/commit-with-validation
Command: npx skills add https://github.com/BerryKuipers/claude-code-toolkit --skill commit-with-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill requires git, jq.

What problem does it solve?

Inconsistent commit messages, missing issue links, and bypassing pre-commit hooks lead to poor git history and quality issues. This Skill ensures every commit adheres to strict git discipline and project standards.

Core Features & Use Cases

  • Standardized Commit Messages: Builds commit messages with conventional format (e.g., feat: subject) and proper GitHub issue linking (Fixes #<issue-number>).
  • Pre-Commit Hook Enforcement: Automatically stages all changes and executes pre-commit hooks, handling failures and auto-fixes without allowing bypass.
  • Atomic Commits: Designed to create a single, atomic commit per feature, ensuring a clean and traceable history.
  • Use Case: As the final step after completing feature implementation and passing all quality gates, use this Skill to create a perfectly formatted and validated commit before pushing.

Quick Start

Example: Create a commit for issue 137 with a subject and body

The skill will prompt for commit type if not provided.

commit-with-validation "Add user dark mode preference toggle" "Implemented dark mode toggle with state management"

This will execute:

git add .

git commit -m "feat: Add user dark mode preference toggle

Implemented dark mode toggle with state management

Fixes #137

šŸ¤– Generated with Claude Code

Co-Authored-By: Claude [email protected]"

Frequently Asked Questions about commit-with-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create standardized git commits with issue linking?ā–¼

Standardized commits follow a conventional format (e.g., `feat: subject`) and automatically link GitHub issues extracted from your branch name. This Skill builds the commit message with proper formatting, stages changes, and enforces pre-commit hooks to ensure every commit meets project standards before pushing.

What happens if pre-commit hooks fail during commit creation?ā–¼

When pre-commit hooks fail, this Skill handles the failure by suggesting either to amend the current commit or create a separate fix commit. It never allows you to bypass hooks, ensuring validation always passes before the commit is finalized.

Can I use this Skill with my existing git workflow?ā–¼

This Skill integrates into WescoBar Git workflows on feature branches after implementation is complete, all tests pass, and your audit score is ≄ 8.0. It requires git and jq as dependencies and creates atomic commits as the final step before opening a pull request.

How do I extract the issue number from my branch name automatically?ā–¼

This Skill extracts the issue number directly from your feature branch name, eliminating manual entry. It then uses that number to automatically add `Fixes #<issue-number>` to your commit message for proper GitHub issue linking.

What's the difference between one atomic commit and multiple commits?ā–¼

Atomic commits group all related changes into a single, traceable unit with a standardized message, creating clean git history. Multiple commits fragment related work and make history harder to follow. This Skill enforces atomic commits to maintain discipline and traceability.

Do I need to stage files manually before using this Skill?ā–¼

No. This Skill automatically stages all changes with `git add .` before constructing and validating your commit. You provide only the commit type, subject, and body; the Skill handles staging and enforcement.