blueprint-review

# Blueprint Review - Security, Quality & PM Compliance Assessment

## Overview

Multi-dimensional code review ensuring **Postmortem compliance**, security compliance, error handling robustness, and validated backtest results before PR creation.

## Core Principle

```
./postmortem/ = 深度病历库 (Deep Case History)
./CLAUDE.md   = 高频手术准则 (High-Frequency Operating Rules)

Rule: PR 不能引入任何已记录在案的反模式，必须通过"病历复查"
```

## When to Use

- Strategy implementation is complete (after `blueprint-develop`)
- Ready to create PR for merge
- User mentions "review", "审核", "PR ready", or "quality check"
- Before any strategy code goes to production

**Do NOT use when:**
- Still implementing features (use `blueprint-develop`)
- Planning phase (use `blueprint-plan`)
- Backtest-only runs without code review intent

## Prerequisites

Before invoking this skill, verify:
- [ ] All tests passing (from `blueprint-develop` Phase 5)
- [ ] **PM regression tests passing** (from `blueprint-develop` Phase 2)
- [ ] Code committed to feature branch
- [ ] Linear ticket linked to the work

## Workflow

```dot
digraph blueprint_review {
    rankdir=TB;
    node [shape=box];

    start [label="Start: Code Ready for Review" shape=ellipse];
    pm_audit [label="0. PM Compliance Audit\n(MANDATORY FIRST)" style=filled fillcolor=lightyellow];
    security [label="1. Security Audit\n(security-guidance)"];
    code_review [label="2. Code Quality Review\n(code-review)"];
    backtest [label="3. Backtest Validation\n(Execute & Capture)"];
    pm_final [label="4. PM Final Check\n(Anti-Pattern Scan)" style=filled fillcolor=lightyellow];
    pr [label="5. Create PR\n(GitHub MCP)"];
    done [label="PR Ready for Human Review" shape=ellipse];

    start -> pm_audit;
    pm_audit -> security;
    security -> code_review;
    code_review -> backtest;
    backtest -> pm_final;
    pm_final -> pr;
    pr -> done;
}
```

## Phase 0: PM Compliance Audit (MANDATORY)

**Goal:** Verify implementation doesn't repeat any documented fai