What are the exit criteria for a successful review?

A successful review requires zero P0 (blocking) issues, zero P1 (critical) issues, and no more than two P2 (suggestion) issues.

At what stage of development should this skill be used?

It is ideally used during the project setup or design phase, specifically after guardrails are drafted but before Low-Level Design (LLD) or implementation begins.

Does Guardrails Reviewer create new engineering rules?

No, the skill is designed to audit and validate existing guardrails for completeness and executability, rather than authoring new rules from scratch.

How does the skill ensure rules are actually executable?

It checks every rule for a defined Rule ID, severity level, and specific verification method to ensure it can be objectively tested during development.

Guardrails Reviewer

Name: Guardrails Reviewer
Author: TestAny-io

byTestAny-io

•

Security & Testing

Validates project engineering standards and guardrails to ensure they are executable, consistent, and ready for implementation.

About

The Guardrails Reviewer is a specialized skill designed to audit project engineering standards (Guardrails) before the Low-Level Design (LLD) or implementation phase. It functions as a quality gate, systematically checking for metadata integrity, scope clarity, rule executability, and consistency with existing tech stacks. By categorizing issues from P0 blockers to P2 suggestions, it ensures that development teams have a solid, verifiable foundation of rules to follow, preventing technical debt and architectural misalignment before coding begins.

Key Features

Standardized issue grading (P0/P1/P2) with strict exit criteria for quality assurance
Automated verification of rule executability and technical stack alignment
Systematic multi-gate review process covering metadata, coverage, and consistency
6 GitHub stars
Generates detailed audit reports and compliance certificates for project documentation
Built-in progress tracking via TodoWrite for phased review management

Use Cases

Validation of existing guardrails against new architectural or technology stack changes
Pre-implementation audit of project engineering standards to ensure they are actionable
Establishing a formal quality gate before moving from the design phase to active development

About

Key Features

Standardized issue grading (P0/P1/P2) with strict exit criteria for quality assurance
Automated verification of rule executability and technical stack alignment
Systematic multi-gate review process covering metadata, coverage, and consistency
6 GitHub stars
Generates detailed audit reports and compliance certificates for project documentation
Built-in progress tracking via TodoWrite for phased review management

Use Cases

Validation of existing guardrails against new architectural or technology stack changes
Pre-implementation audit of project engineering standards to ensure they are actionable
Establishing a formal quality gate before moving from the design phase to active development