code-review-policy

Classify LLM-generated code review findings into severity-labeled reports with reproducible evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy reduces inconsistent or non-actionable LLM-driven code review findings by defining severity levels, evidence rules, pass/fail gates, and escalation criteria so reviews are reproducible and decision-ready.

Core Features & Use Cases

  • Standardized severity taxonomy (S0–S3) that differentiates blockers, critical, major, and minor issues for RTL and verification artifacts.
  • Pass/fail gating rules that require remediation for high-severity items and conditional acceptance for medium-severity findings.
  • Evidence requirements that mandate file/line references, failing command or log snippets, expected versus actual behavior, and replay artifacts where available.
  • Escalation guidance for immediate stops on data-corrupting issues and routing repeat critical failures to architecture owners.
  • Use case: audit an RTL module and produce a findings table with reproducible evidence and required remediation steps for the team and stakeholders.

Quick Start

Apply the policy to classify each review finding with severity, attach reproducible evidence, and generate the Code Review Report with verdict, findings, required actions, and escalations.

Frequently Asked Questions about code-review-policy

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

FAQPage Schema
How do I standardize LLM code review findings for RTL and verification artifacts?

To standardize LLM code review findings for RTL and verification artifacts, apply a policy that classifies issues using a severity taxonomy like S0-S3 and enforces pass/fail gating. This ensures reviews are reproducible and decision-ready.

What is the best way to attach reproducible evidence to an LLM code review report?

The best way to attach reproducible evidence to an LLM code review report is to mandate file and line references, failing command or log snippets, and expected versus actual behavior for every finding.

How do you define severity levels and escalation rules for silicon risk assessments?

Severity levels for silicon risk assessments differentiate blockers, critical, major, and minor issues. Escalation rules mandate immediate stops for data-corrupting issues and route repeat critical failures to architecture owners.

Can I use a code review policy to generate actionable remediation steps for my team?

Yes, you can use a code review policy to generate actionable remediation steps. It produces a structured report skeleton containing the verdict, findings, required actions, and escalations needed for team remediation.

What are the limitations of using non-standardized LLM code reviews for testbench quality?

Non-standardized LLM code reviews for testbench quality often produce inconsistent or non-actionable findings. Without severity gating and evidence requirements, reviews lack reproducibility and fail to provide decision-ready remediation.