actionable-review-format-standards

Actionable Review Format Standards

Standardized output format for code reviews ensuring consistent, actionable, and prioritized feedback across all reviewer agents.

When to Use This Skill

• Generating code review reports
• Formatting PR feedback
• Creating security audit reports
• Producing performance review outputs
• Any review output requiring severity classification

Core Principles

1. Every issue has a severity - Never leave findings unclassified
2. Every issue has a location - Always include file:line references
3. Every blocking issue has a fix - Provide code snippets for Critical/High
4. Summary before details - Lead with counts and verdicts
5. Categorize by concern - Group Security, Performance, Patterns separately

---

Severity Classification

Severity Levels

Level	Icon	Criteria	Action Required
CRITICAL	🔴	Security vulnerabilities, data loss risk, system crashes	Must fix before merge
HIGH	🟠	Significant bugs, missing authorization, performance blockers	Should fix before merge
MEDIUM	🟡	Code quality issues, minor bugs, missing validation	Fix soon, not blocking
LOW	🟢	Style issues, minor improvements, suggestions	Nice to have
INFO	💡	Educational comments, alternative approaches	No action required

Severity Decision Tree

Is it a security vulnerability?
├── Yes → CRITICAL
└── No → Can it cause data loss or corruption?
         ├── Yes → CRITICAL
         └── No → Can it cause system crash/downtime?
                  ├── Yes → HIGH
                  └── No → Does it break functionality?
                           ├── Yes → HIGH
                           └── No → Does it affect performance significantly?
                                    ├── Yes → MEDIUM
                                    └── No → Is it a code quality issue?
                                             ├── Yes → MEDIUM/LOW
                                             └── No → LOW/INFO