verification-recheck-policy

Map code change types to minimum verification checks with pass/fail criteria.

43|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/babyworm/rtl-agent-team --skill verification-recheck-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-recheck-policy
Source: https://github.com/babyworm/rtl-agent-team/tree/main/skills/verification-recheck-policy
Command: npx skills add https://github.com/babyworm/rtl-agent-team --skill verification-recheck-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures reviewers and engineers run the appropriate minimum set of verification activities after code review or refactor work so that style, functional, CDC, synthesis, and equivalence risks are neither under- nor over-checked and that failures are reproducible and escalated properly.

Core Features & Use Cases

  • Change-type matrix: Maps change categories (style-only, logic refactor, interface-impact, constraint/synthesis-impact) to the minimum verification activities required.
  • Pass/fail and escalation rules: Defines clear criteria for lint, CDC, functional/regression, synthesis/timing, and equivalence checks and when to escalate.
  • Operational guidance: Provides recommended open-source commands and replay guidance to generate reproducible artifacts for audits and debugging.
  • Use case: After an interface-impact change, quickly determine the required CDC, functional regression, and equivalence checks and produce a recheck report with artifacts for design owners.

Quick Start

Generate a verification recheck matrix for an interface-impact change that lists required lint, CDC, functional regression, synthesis/timing rerun, equivalence checks, pass/fail criteria, and escalation steps.

Frequently Asked Questions about verification-recheck-policy

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

FAQPage Schema
What minimum verification steps are required after an RTL logic refactor?

Minimum verification steps after an RTL logic refactor include lint, functional regression, and equivalence checks to ensure functional behavior is preserved without under- or over-checking.

How do I determine which recheck matrix to run for an interface-impact change?

For an interface-impact change, the recheck matrix requires CDC, functional regression, synthesis/timing rerun, and equivalence checks, plus defined pass/fail and escalation criteria for reproducible audits.

Do I need to rerun CDC and synthesis checks for style-only RTL changes?

Style-only RTL changes do not require CDC, synthesis, or equivalence rechecks; the minimum re-validation matrix maps them to only the essential lint checks to prevent unnecessary verification overhead.

What is the best way to enforce minimal re-validation for RTL and verification projects?

The best way to enforce minimal re-validation is to apply a change-type matrix that categorizes modifications and dictates the exact lint, CDC, functional, synthesis, and equivalence checks required.

How to generate a reproducible recheck report for synthesis and constraint changes?

Generate a reproducible recheck report by running recommended open-source commands for synthesis/timing rerun and equivalence checks, capturing artifacts that define clear pass/fail criteria for audits.

When should I escalate failures during RTL regression and equivalence checks?

Escalate failures during RTL regression and equivalence checks when results violate the predefined pass/fail criteria in the re-validation matrix, triggering proper escalation steps for design owners.