review-gates

Enforce project-specific review criteria with kspec during code reviews.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/lepahc/kynetic-spec --skill review-gates-lepahc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-gates
Source: https://github.com/lepahc/kynetic-spec/tree/main/.agents/skills/review-gates
Command: npx skills add https://github.com/lepahc/kynetic-spec --skill review-gates-lepahc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project-specific review criteria for this codebase, ensuring reviews consistently enforce severity classifications, regression checks, and an anti-rubber-stamping checklist.

Core Features & Use Cases

  • Severity Classification: categorize findings as MUST-FIX, SHOULD-FIX, or SUGGESTION to prioritize remediation.
  • Regression & Quality Checks: verify tests align with spec, detect regressions, and ensure changes meet acceptance criteria.
  • Anti-Rubber-Stamping: mandate evidence-backed approvals and documented rationale to prevent premature merges.

Quick Start

Review a pull request against the defined gates and record the outcome in the review system.

Frequently Asked Questions about review-gates

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

FAQPage Schema
How do I prevent rubber-stamping in code reviews?

Code review severity classifications categorize findings as MUST-FIX, SHOULD-FIX, or SUGGESTION to prioritize remediation. This standardized handling ensures critical issues block merges while minor improvements remain optional.

How do I enforce project-specific review gates across repositories?

Regression checks during code reviews verify that tests align with the specification and ensure changes meet acceptance criteria. This process detects regressions early and validates that modifications fulfill project requirements.

What is the best way to automate code review quality checks?

Automating code review quality checks involves applying project-specific review criteria to validate pull requests, enforce severity classifications, and mandate anti-rubber-stamping checklists. This integration ensures consistent quality enforcement across repositories using kspec.

Does kspec support enforcing severity classifications in pull requests?

Yes, kspec supports enforcing severity classifications in pull requests by categorizing findings as MUST-FIX, SHOULD-FIX, or SUGGESTION. This integration with the core $kspec-review skill ensures consistent severity handling and prevents premature merges.