Code review policy
Internal reference: code review policy (agent-loaded; do not invoke).From its SKILL.md
npx -y skills add babyworm/rtl-agent-team --skill code-review-policyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.7 KB, as published. Nobody here has run it
Code Review Policy
Scope
- RTL logic correctness and spec/uarch compliance
- Testbench quality and checker/scoreboard adequacy
- Verification completeness (coverage + traceability)
- Silicon risk indicators (constraints/CDC/synthesis/timing impacts)
Severity
S0 Blocker: data corruption, protocol/safety breakage, hard spec violationS1 Critical: high silicon risk, functional failure likely under valid stimulusS2 Major: maintainability/test-quality issues with medium defect riskS3 Minor: style/readability/non-blocking improvements
Pass/Fail Gate
FAIL: any unresolvedS0orS1CONDITIONAL: onlyS2findings remain and have approved remediation planPASS: onlyS3or no findings
Escalation
- Any
S0: immediate stop, escalate to orchestrator/user with fix-first recommendation - Repeated
S1on same module after 2 fix loops: escalate to architecture owner - Missing evidence for
S0/S1: finding is invalid until evidence attached
Evidence Rules
- Every
S0/S1finding must include reproducible evidence:- file and line
- failing command/log snippet
- expected vs actual behavior
- Prefer replay artifacts (
*_latest.sh, wave/report paths) over prose-only claims
Output Format
Use the following report skeleton:
# Code Review Report
- Scope: module|block|top
- Verdict: PASS | CONDITIONAL | FAIL
## Findings
| ID | Severity | File:Line | Summary | Evidence |
|---|---|---|---|---|
## Required Actions
| Priority | Owner | Action | Recheck |
|---|---|---|---|
## Escalations
- [if any]