# Project Diff Review Skill

## Trigger
`/project-diff [absolute_path] [commit_range or PR#]` or "변경분 리뷰", "PR 리뷰"

## Description
Targeted review of a specific commit range or PR. Only analyzes changed files against the existing audit baseline. Much faster than full audit.

## Input
- Absolute project path
- Commit range (e.g., `HEAD~3..HEAD`) or PR number
- Optional: previous audit report for delta comparison

## Execution Workflow

### Step 1: Identify Changes
- `git diff --name-only [range]` to get changed files
- Categorize changes: new files, modified files, deleted files

### Step 2: Targeted Analysis (only relevant agents)
- Changed source files → `dev-code-quality`, `dev-architecture`
- Changed security-related files → `dev-security`
- Changed package files → `dev-supply-chain`
- Changed test files → `dev-test-coverage`
- Changed docs → `dev-docs-sync`
- Changed CI/config → `dev-devops`
- Performance-sensitive changes → `dev-performance`

### Step 3: Impact Assessment
- Does this change improve or degrade each dimension?
- New technical debt introduced?
- Existing issues fixed?

## Output Format
Final deliverable in **Korean (한국어)**.

```markdown
# [Project Name] Diff Review — [commit range]

## Changes Summary
- Files changed: [count]
- Lines added: [count]
- Lines removed: [count]

## Review Results
| File | Agent | Finding | Severity |
|------|-------|---------|----------|
| | | | |

## Health Score Impact
| Dimension | Before | After | Delta |
|-----------|--------|-------|-------|

## Approval Status
- [ ] Security: PASS/FAIL
- [ ] Architecture: PASS/FAIL
- [ ] Tests: PASS/FAIL
- [ ] Docs updated: PASS/FAIL

## Verdict: [✅ APPROVE / ⚠️ REQUEST CHANGES / 🔴 BLOCK]
```

## Brutal Analysis Principles
- A diff that adds code without tests should be flagged
- A diff that changes API without updating docs should be flagged
- Security regressions = automatic BLOCK

## Claude-Gemini Cross-Debate Protocol
For diff reviews, Claude analyzes → Gemini reviews the same diff → consensus on verdict.
