rulebook-quality-gates

Enforce automated quality gates on code changes before commits and pushes.

15|2|Updated Oct 23, 2025

Search Tags:#quality #pre-commit #coverage #lint #ci #tests #git-hooks

Ready to run

npx skills add https://github.com/hivellm/rulebook --skill rulebook-quality-gates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rulebook-quality-gates
Source: https://github.com/hivellm/rulebook/tree/main/skills/rulebook-quality-gates
Command: npx skills add https://github.com/hivellm/rulebook --skill rulebook-quality-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes often bypass quality checks, leading to defects slipping into production. This Skill defines automated gates that verify essential quality criteria before changes are committed or merged, reducing regressions and rework.

Core Features & Use Cases

Pre-commit & pre-push checks: Ensure code adheres to type safety, formatting, linting, and test coverage before commits and pushes.
Quality thresholds: Enforce zero warnings, 100% test pass rates, and high coverage to maintain code health across projects.
Git hook installation: Optional integration with the Rulebook CLI to install and manage pre-commit and pre-push hooks.

Quick Start

rulebook init # Install and configure quality gates as Git hooks for your repo rulebook status # Show current gate configuration and thresholds

Frequently Asked Questions about rulebook-quality-gates

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

FAQPage Schema

How do I enforce code quality checks before a git commit?▼

To enforce code quality before a git commit, you configure automated pre-commit and pre-push workflows using Git hooks. This validates type-checking, linting, formatting, and test coverage to ensure code adheres to quality thresholds before changes are committed.

What is the best way to prevent untested code from being pushed to a repository?▼

The best way to prevent untested code from being pushed is to enforce quality gates via pre-push Git hooks. This mechanism verifies 100% test pass rates and high coverage thresholds, automatically blocking pushes if tests fail or coverage drops below required levels.

Can I use CI environments to enforce linting and test coverage thresholds?▼

Yes, you can enforce linting and test coverage thresholds in CI environments. By integrating quality gates into your continuous integration pipelines, you validate type safety and formatting standards across local development and CI workflows to maintain code health.

How do I install and manage Git hooks for pre-commit checks?▼

You install and manage Git hooks for pre-commit checks using standard tooling and the Rulebook CLI. Running the initialization command sets up the hook configurations, while the status command displays current gate configurations and coverage thresholds.

Why do code changes bypass quality checks in standard workflows?▼

Code changes bypass quality checks in standard workflows when automated gates are missing, allowing defects to slip into production. Integrating pre-commit and pre-push gates ensures type safety and formatting are verified before changes are merged, reducing regressions and rework.