review-output-format

What problem does it solve?

Unstructured, inconsistent code review output makes it difficult for engineering teams to prioritize critical issues, track actionable fixes, and integrate review feedback into downstream project management and development workflows. This Skill eliminates that friction by enforcing a strict, uniform format for all review findings.

Core Features & Use Cases

• Strict JSON Schema Enforcement: Ensures all review output is a valid JSON object with a required top-level findings array, eliminating malformed output that breaks downstream tooling.
• Severity-Based Sorting: Mandates that findings are ordered by risk (highest first) so critical blockers and major issues are addressed immediately, rather than getting lost in unstructured feedback.
• Standardized Rubric Fields: Requires non-trivial findings to include clear context (why, scope), risk assessment (risk_if_unchanged), concrete evidence, and actionable change_request details, so every review comment is clear and actionable.
• Use Case: For engineering teams running pull request reviews or code audits, this Skill ensures all feedback is uniform, easy to triage, and compatible with issue tracking and reporting tools.

Quick Start

Use the review-output-format skill to format all identified code review findings into a valid, severity-sorted JSON object with complete rubric details for each actionable issue.