pr-review-output

# PR Review Output Format

This skill standardizes the format of PR review reports that aggregate findings from multiple specialized agents.

## Report Structure

The final PR review report MUST follow this structure:

```markdown
# PR Review Report

**PR/Changes:** [Branch name or PR title]
**Reviewed:** [Date]
**Agents Used:** [List of agents that ran]

---

## Executive Summary

**Overall Verdict:** ✅ Approved | ⚠️ Approved with Comments | 🔶 Changes Requested | ❌ Blocked

**Risk Level:** 🟢 Low | 🟡 Medium | 🟠 High | 🔴 Critical

| Category | Issues | Critical | High | Medium | Low |
|----------|--------|----------|------|--------|-----|
| Architecture | X | X | X | X | X |
| Code Quality | X | X | X | X | X |
| Bugs | X | X | X | X | X |
| Requirements | X | X | X | X | X |
| Security | X | X | X | X | X |
| Tests | X | X | X | X | X |
| Performance | X | X | X | X | X |
| **Total** | **X** | **X** | **X** | **X** | **X** |

### Key Findings
1. [Most critical finding - one sentence]
2. [Second most critical]
3. [Third most critical]

---

## Critical & High Priority Issues

[Only issues with Critical or High severity, grouped and deduplicated]

### 🔴 Critical Issues (Must Fix)

#### [CATEGORY-XXX] Issue Title
**Agent:** [Which agent found this]
**Location:** `file/path.ts:line_number`

[Issue description]

**Fix:**
```[language]
// solution code
```

---

### 🟠 High Priority Issues (Should Fix)

[Same format as Critical]

---

## Medium & Low Priority Issues

[Collapsed or summarized for readability]

### 🟡 Medium Priority (X issues)

| ID | Issue | Location | Agent |
|----|-------|----------|-------|
| CLEAN-001 | Variable naming | `src/file.ts:42` | Code Cleaner |
| ... | ... | ... | ... |

### 🟢 Low Priority (X issues)

[Same table format]

---

## Positive Observations

What the code does well:

- ✅ [Positive aspect from Architect]
- ✅ [Positive aspect from Code Cleaner]
- ✅ [Positive aspect from Tests]

---

## Recommended Actions

### Before Merge (R