commit-protocol

Run pnpm lint and type-check in parallel before requiring explicit user approval for git commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nizarghribi/hounii-monorepo-first --skill commit-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-protocol
Source: https://github.com/nizarghribi/hounii-monorepo-first/tree/main/.claude/skills/commit-protocol
Command: npx skills add https://github.com/nizarghribi/hounii-monorepo-first --skill commit-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent commit messages, failed quality checks, and untested code can lead to messy Git history, broken builds, and wasted development time. This Skill enforces a rigorous commit protocol, ensuring every change is thoroughly tested and adheres to project standards before being committed.

Core Features & Use Cases

  • Automated Quality Gates: Automatically runs lint and type-check before any commit, preventing common errors from entering the codebase.
  • Guided Testing & Approval: Provides clear, actionable testing instructions and requires explicit user confirmation, guaranteeing code functionality.
  • Conventional Commit Enforcement: Ensures all commits follow the project's conventional commit format, leading to a clean, readable, and searchable Git history.
  • Use Case: After implementing a new feature, use this Skill to guide you through the final checks, ensuring your code passes all quality gates, is manually tested, and committed with a perfectly formatted message.

Quick Start

Use the commit-protocol skill to commit my recent changes to the 'mobile' app, after I have manually tested them.

Frequently Asked Questions about commit-protocol

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

FAQPage Schema
How do I prevent untested code from being committed to git?

Enforce a commit protocol that runs automated quality checks like linting and type-checking before allowing commits. This blocks code with errors and requires explicit user approval, ensuring only tested changes enter the repository.

What quality gates should run before committing code?

Run linting and type-checking in parallel to catch common errors automatically. The commit-protocol enforces these checks, fixing all errors before proceeding and requiring manual testing confirmation from you before finalizing the commit.

How do I ensure consistent commit messages across my team?

Enforce conventional commit format through an automated protocol that validates message structure before accepting commits. This produces a clean, searchable Git history and prevents inconsistent messages from entering the codebase.

Can I automate testing steps before each commit?

Yes. A commit protocol guides you through explicit testing instructions, runs quality checks automatically, and blocks commits until all errors are fixed and manual testing is confirmed, eliminating human oversight gaps.

What happens if my code fails linting or type-checking during commit?

The protocol halts the commit, surfaces the errors, and requires you to fix them before proceeding. Only after all checks pass and you provide explicit approval does the commit finalize.

Do I need to manually test code before committing?

Yes. The protocol requires explicit user confirmation after providing concrete testing instructions, guaranteeing manual verification occurs. This prevents untested commits and catches functional issues before they reach the repository.

Related Skills