litisaude/skills/review

/review — Composite Code Review

Run the appropriate reviewer agents based on the mode and stack.

Usage

• /review plan — Review a plan/feature description before coding. Produces a requirements checklist.
• /review code — Review actual code changes. Produces a violation report.
• /review code backend — Limit code review to backend reviewers only.
• /review code frontend — Limit code review to frontend reviewers only.

Mode: plan

When: Before coding starts. The user has a feature description or plan draft.

What it does: Launches three agents in parallel — one for engineering standards (@agents/plan-requirements-reviewer.md), one for business/product readiness (@agents/business-readiness-reviewer.md), and one for security & threat modeling (@agents/security-threat-modeling-reviewer.md). Together they produce a comprehensive review covering technical requirements, business blind spots, and design-level security gaps. No code scanning.

Behavior:

1. Read the user's feature description or plan draft from context.
2. Launch three Task agents in parallel with subagent_type: "general-purpose":
   • One with the prompt from @agents/plan-requirements-reviewer.md (engineering standards)
   • One with the prompt from @agents/business-readiness-reviewer.md (business/product readiness)
   • One with the prompt from @agents/security-threat-modeling-reviewer.md (security & threat modeling)
3. Merge results into a single report.

Mode: code

When: After coding. The user has made changes and wants them reviewed.

What it does: Launches specialized reviewer agents in parallel to scan actual code for violations.

Behavior:

1. Determine scope: Look at the files the user wants reviewed. If no files are specified, use recent git changes (git diff --name-only HEAD~1).

2. Detect stack (if not explicitly provided):

   • Backend indicators: .py, .go, .java, .rs files, models/, api/, services/, domains/, background_jobs/
   • Frontend/mobile indicators: .tsx, .jsx, .ts, .js, .swift, .kt, .dart files, components/, screens/, pages/, hooks/
   • If mixed, run all relevant reviewers.

3. Launch reviewers in parallel using the Task tool with subagent_type: "general-purpose":

   For backend code, launch three parallel agents:

   • One with the prompt from @agents/production-hardening-reviewer.md scoped to the target files
   • One with the prompt from @agents/audit-compliance-reviewer.md scoped to the target files
   • One with the prompt from @agents/security-controls-reviewer.md scoped to the target backend files (backend pillars only)

   For frontend/mobile code, launch three parallel agents:

   • One with the prompt from @agents/production-hardening-reviewer.md scoped to the target frontend files (frontend pillars only — kill switch, client resilience)
   • One with the prompt from @agents/analytics-coverage-reviewer.md scoped to the target files
   • One with the prompt from @agents/security-controls-reviewer.md scoped to the target frontend files (frontend pillars only)

   For mixed stack, launch all four agents — a single production-hardening invocation covering both stacks, audit-compliance, analytics-coverage, and a single security-controls-reviewer invocation that covers both backend and frontend pillars across the full file scope.

4. Merge results: Combine the outputs from all agents into a single report.

Output Format

Plan mode

# Plan Review: [Feature Name]

## Stack: [Backend / Frontend / Full Stack]

## Engineering Requirements

### [Category]
- ⚠️ **[Requirement]**: Why it applies and what the plan should specify
- ✅ **[Requirement]**: Already addressed in the plan

## Business & Product Readiness

### [Pillar Name]
- ⚠️ **[Requirement]**: Why it applies and what the plan should specify
- ✅ **[Requirement]**: Already addressed in the plan

## Security & Threat Model

### [Pillar Name]
- ⚠️ **[Requirement]**: Why it applies and what the plan should specify
- ✅ **[Requirement]**: Already addressed in the plan

## Summary
- **Engineering gaps**: N items
- **Business/product gaps**: N items
- **Security gaps**: N items
- **Already covered**: N items

Code mode

# Code Review Report

## Stack: [Backend / Frontend / Full Stack]
## Files reviewed: [list or summary]

---

## Production Hardening
[Output from production-hardening-reviewer]

---

## Audit Compliance
[Output from audit-compliance-reviewer]

---

## Security Controls
[Output from security-controls-reviewer]

---

## Analytics Coverage
[Output from analytics-coverage-reviewer]

---

## Summary
- **Critical**: N findings
- **High**: N findings
- **Medium**: N findings
- **Low**: N findings