commit

Enforce quality gates and conventional commit rules in Git workflows.

41|7|Updated Jan 30, 2026

Search Tags:#git #workflow #commit #hooks #code-quality #ci #conventional-commits

Ready to run

npx skills add https://github.com/DGouron/review-flow --skill commit-dgouron

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/DGouron/review-flow --skill commit-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures safe Git commits and pushes by enforcing quality gates and conventional commit rules, reducing broken builds and misformatted messages.

Core Features & Use Cases

Enforces pre-commit checks (TypeScript, lint) and commit message formats.
Blocks pushes to protected branches and validates specs before changes reach main.
Guides users through a structured, compliant commit workflow with auto-verification.

Quick Start

Ask Claude to perform a safe commit on the current changes and push once all checks pass.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate conventional commit messages with pre-commit hooks?▼

To automate conventional commits with pre-commit hooks, use Husky and Claude Code hooks to enforce quality gates like TypeScript and lint checks, then format commit messages to a conventional style before changes reach main.

What is a safe Git commit workflow for feature branches?▼

A safe Git commit workflow for feature branches restricts pushes to protected branches, validates specs through automated hooks, and enforces pre-commit checks to reduce broken builds and misformatted messages before merging to main.

Does Husky work with Claude Code hooks to block pushes to main?▼

Yes, Husky works with Claude Code hooks to block pushes to protected branches like main. It restricts main access, validates specs, and guides users through a structured commit workflow with auto-verification on feature branches.

How do I enforce conventional commit rules in GitHub or GitLab?▼

Enforcing conventional commit rules in GitHub or GitLab involves using hooks that guide user prompts, validate specs on feature branches, and format commit messages to a conventional style, preventing misformatted messages from reaching main.

Can I validate specs before a Git commit reaches the main branch?▼

Yes, you can validate specs before a Git commit reaches main by using Claude Code hooks to enforce quality gates on feature branches. This restricts main access and ensures automated checks pass before merging changes.

Why do my Git pushes fail when conventional commit checks are enforced?▼

Git pushes fail when conventional commit checks are enforced because quality gates detect TypeScript or lint errors, or the commit message format is invalid. The hooks block pushes to protected branches until all checks pass.