菜单
Create normalized opForge review reports with findings-first structure, stable finding IDs, evidence-based severity, and explicit testing gaps. Use when a code review needs to be written, cleaned up, or merged from multiple reviewers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create execution-ready opForge plans from specs, reviews, or explicitly scoped user requests. Use when implementation or remediation work needs ordered, commit-sized slices with checkboxes, validations, and definition-of-done rules.
Verify and document that claimed review fixes actually close the original opForge findings. Use when remediation work claims to resolve prior review items and closure evidence must be recorded.
Write implementation-ready opForge specifications with explicit goals, non-goals, invariants, acceptance criteria, and validation expectations. Use when behavior needs to be designed before planning or coding begins.
| name | opforge-review-reporting |
| description | Create normalized opForge review reports with findings-first structure, stable finding IDs, evidence-based severity, and explicit testing gaps. Use when a code review needs to be written, cleaned up, or merged from multiple reviewers. |
Use templates/review-report-template.md without changing its validator-facing headings.
Each material finding includes:
RVW-YYYY-MM-DD-NNN finding IDscripts/workflow/allocate_review_finding_id.pyscripts/workflow/check_review_report.pyscripts/workflow/check_workflow_artifact_bundle.pyscripts/workflow/run_review_workflow.sh