skills.rest
notque
notqueCOMMUNITY
Explore all skills by this author →
GitHub

git-commit-flow

Automate phase-gated git commit workflows with validation, staging, and CLAUDE.md compliance.

415|44|Updated Mar 18, 2026
Search Tags:#git#workflow#security#commit#validation#conventional-commits
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill git-commit-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-flow
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/git-commit-flow
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill git-commit-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Phase-gated git commit workflow that enforces validation, staging discipline, and CLAUDE.md compliance, reducing human error and drift in project history.

Core Features & Use Cases

  • 4-phase workflow: VALIDATE, STAGE, COMMIT, VERIFY to ensure each step completes deterministically.
  • Enforces conventional commit formats and bans patterns that degrade history quality.
  • Scans for sensitive files, groups changes for atomic commits, and guides user through staged plans.
  • Works across PR workflows and standard git operations to enforce policy without manual overhead.

Quick Start

Invoke the git-commit-flow skill on a set of changes and follow the four-phase prompts to validate, stage, commit, and verify.

Frequently Asked Questions about git-commit-flow

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

FAQPage Schema
How do I automate git commit validation and enforce conventional commit formats?▼

Yes, you can block sensitive files during git staging by using a validation phase that scans for restricted patterns and sensitive data before proceeding to stage and commit changes, preventing accidental exposure of secrets.

What is the best way to enforce a standardized git commit workflow across a team?▼

Git commit validation works by passing changes through four distinct phases: VALIDATE checks for banned patterns and sensitive files, STAGE groups changes for atomic commits, COMMIT applies conventional formats, and VERIFY confirms the result.

Can I do a dry run of my git commit workflow before pushing changes?▼

Yes, the workflow supports PR workflows and standard git operations by enforcing commit policies and staging discipline across both contexts, ensuring consistent history quality without manual overhead.

Why should I use a phase-gated git commit process instead of standard git commands?▼

You will need an existing git repository with pending changes and a CLAUDE.md file if project compliance is required, as the workflow validates changes against these standards before allowing a commit.

Related Skills

Explore More Software Engineering Skills→
EhraxEhrax

using-git-worktrees

Creates isolated git worktrees for feature work with verified ignore rules and project setup.

Community
Advanced
malinskibeniaminmalinskibeniamin
3

commit-push-pr

Automate commit, push, and pull request creation with CI monitoring.

Community
Advanced
RedHatProductSecurityRedHatProductSecurity
47

semgrep

Automate static code analysis for security vulnerabilities across multi-language repositories.

Official
Intermediate
JackSmack1971JackSmack1971

git-commit-standards

Configure pre-commit hooks to validate conventional commit messages.

Community
Intermediate