digraph review_pr {
    rankdir=TB;
    node [shape=box];

    start [label="PR URL/Number" shape=ellipse];

    subgraph cluster_fetch {
        label="1. PARALLEL Fetch Context";
        style=dashed;
        pr [label="Fetch PR details\n(title, body, files, commits)"];
        issues [label="Fetch referenced issues\n(requirements, acceptance criteria)"];
        comments [label="Fetch PR/issue comments\n(QA feedback, discussions)"];
    }

    analyze [label="2. Parse scope & extract keywords"];

    subgraph cluster_skills {
        label="3. PARALLEL Skill-Based Reviews (10 agents)";
        style=dashed;
        react [label="React Best Practices"];
        rn [label="React Native Best Practices"];
        composition [label="Composition Patterns"];
        native_ui [label="Native UI Design"];
        frontend [label="Frontend Design"];
        vercel_rn [label="Vercel RN Skills"];
        expo_deploy [label="Expo Deployment"];
        expo_dev [label="Expo Dev Client"];
        data_fetch [label="Native Data Fetching"];
        expo_upgrade [label="Expo Upgrade Compat"];
    }

    merge [label="4. Merge & Deduplicate Issues"];

    issues_cat [label="5. Categorize Issues\n- P0: Critical (blocks merge)\n- P1: High (before merge)\n- P2: Medium (follow-up)"];

    gist [label="6. Create private gist"];
    done [label="Return gist URL" shape=ellipse];

    start -> pr;
    start -> issues;
    start -> comments;
    pr -> analyze;
    issues -> analyze;
    comments -> analyze;
    analyze -> react;
    analyze -> rn;
    analyze -> composition;
    analyze -> native_ui;
    analyze -> frontend;
    analyze -> vercel_rn;
    analyze -> expo_deploy;
    analyze -> expo_dev;
    analyze -> data_fetch;
    analyze -> expo_upgrade;
    react -> merge;
    rn -> merge;
    composition -> merge;
    native_ui -> merge;
    frontend -> merge;
    vercel_rn -> merge;
    expo_deploy -> merge;
    expo_dev -> merge;
    data_fetch -> merge;
    expo_upgrade -> merge;
    merge -> issues_cat -> gist -> done;
}

# PR details
gh pr view <NUMBER> --json title,body,commits,files,comments,reviews,labels,state,headRefName,baseRefName

# Referenced issues (parse from PR body "fixes #XXXX")
gh issue view <ISSUE_NUMBER> --json title,body,comments,labels,state

# Get diff stats
gh pr diff <NUMBER> --stat

Review the PR changes against React best practices from the vercel-react-best-practices skill.

Check:
1. Component composition patterns
2. State management (useState, useReducer)
3. Effect cleanup and dependencies
4. Memoization (useMemo, useCallback, React.memo)
5. Key prop usage in lists
6. Prop drilling vs context
7. Error boundaries
8. Suspense and lazy loading

Report violations with file paths and line numbers.

Review the PR changes against React Native best practices from the react-native-best-practices skill.

Check:
1. FPS and performance (avoid JS thread blocking)
2. FlashList vs FlatList usage
3. Native driver animations
4. Bridge overhead minimization
5. Memory leaks (cleanup, subscriptions)
6. Image optimization
7. Hermes-specific optimizations
8. Bundle size impact

Report violations with file paths and line numbers.

Review the PR changes against React composition patterns from the vercel-composition-patterns skill.

Check:
1. Boolean prop proliferation
2. Compound component patterns
3. Render props usage
4. Context provider design
5. Slot patterns
6. Inversion of control
7. Component API flexibility
8. Reusability vs specificity

Report violations with file paths and line numbers.

Review the PR changes against Native UI design guidelines from the building-native-ui skill.

Check:
1. Expo Router patterns
2. Navigation structure
3. Animation implementation
4. Native tabs configuration
5. Component styling patterns
6. Layout consistency
7. Platform-specific handling
8. Accessibility considerations

Report violations with file paths and line numbers.

Review the PR changes against frontend design guidelines from the frontend-design skill.

Check:
1. Visual hierarchy
2. Spacing and typography
3. Color usage and theming
4. Responsive design patterns
5. Interactive states (hover, press, focus)
6. Loading and error states
7. Empty states
8. Design system consistency

Report violations with file paths and line numbers.

Review the PR changes against Vercel React Native skills from the vercel-react-native-skills skill.

Check:
1. List virtualization
2. Animation performance
3. Native module integration
4. Gesture handling
5. Image caching
6. Network request patterns
7. Offline support
8. Platform-specific code organization

Report violations with file paths and line numbers.

Review the PR changes against Expo deployment guidelines from the expo-deployment skill.

Check:
1. EAS Build configuration
2. App store deployment readiness
3. Environment variables handling
4. OTA update compatibility
5. Native module compatibility
6. Build profiles configuration
7. Submission credentials
8. Release channel management

Report violations with file paths and line numbers.

Review the PR changes against Expo dev client guidelines from the expo-dev-client skill.

Check:
1. Development build configuration
2. Custom native module integration
3. Debug vs release behavior
4. TestFlight/Internal distribution setup
5. Local development workflow
6. Native dependency management
7. Build caching strategies
8. Development plugin usage

Report violations with file paths and line numbers.

Review the PR changes against native data fetching guidelines from the native-data-fetching skill.

Check:
1. Fetch API usage patterns
2. Error handling and retries
3. Caching strategies
4. Offline support implementation
5. Request cancellation
6. Loading state management
7. Optimistic updates
8. Background refresh patterns

Report violations with file paths and line numbers.

Review the PR changes against Expo upgrade guidelines from the upgrading-expo skill.

Check:
1. SDK version compatibility
2. Deprecated API usage
3. Breaking change impact
4. Native module version alignment
5. Config plugin compatibility
6. Dependency version conflicts
7. Migration path requirements
8. Testing requirements post-upgrade

Report violations with file paths and line numbers.

digraph skill_review {
    rankdir=TB;
    node [shape=box];

    pr_files [label="PR Changed Files" shape=ellipse];

    subgraph cluster_parallel {
        label="PARALLEL Skill-Based Reviews (10 agents)";
        style=dashed;
        react [label="React Best Practices"];
        rn [label="React Native Best Practices"];
        composition [label="Composition Patterns"];
        native_ui [label="Native UI Design"];
        frontend [label="Frontend Design"];
        vercel_rn [label="Vercel RN Skills"];
        expo_deploy [label="Expo Deployment"];
        expo_dev [label="Expo Dev Client"];
        data_fetch [label="Native Data Fetching"];
        expo_upgrade [label="Expo Upgrade Compat"];
    }

    merge [label="Merge & Deduplicate Issues"];
    categorize [label="Categorize by Severity\n(P0/P1/P2)"];

    pr_files -> react;
    pr_files -> rn;
    pr_files -> composition;
    pr_files -> native_ui;
    pr_files -> frontend;
    pr_files -> vercel_rn;
    pr_files -> expo_deploy;
    pr_files -> expo_dev;
    pr_files -> data_fetch;
    pr_files -> expo_upgrade;
    react -> merge;
    rn -> merge;
    composition -> merge;
    native_ui -> merge;
    frontend -> merge;
    vercel_rn -> merge;
    expo_deploy -> merge;
    expo_dev -> merge;
    data_fetch -> merge;
    expo_upgrade -> merge;
    merge -> categorize;
}

Use a SINGLE message with 10 Task tool calls:

Task 1:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against vercel-react-best-practices skill..." }
Task 2:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against react-native-best-practices skill..." }
Task 3:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against vercel-composition-patterns skill..." }
Task 4:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against building-native-ui skill..." }
Task 5:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against frontend-design skill..." }
Task 6:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against vercel-react-native-skills skill..." }
Task 7:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against expo-deployment skill..." }
Task 8:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against expo-dev-client skill..." }
Task 9:  { subagent_type: "superpowers:code-reviewer", prompt: "Review against native-data-fetching skill..." }
Task 10: { subagent_type: "superpowers:code-reviewer", prompt: "Review against upgrading-expo skill..." }

gh gist create -d "PR #<NUM>: <Title> - Review" analysis.md

# PR #<NUM>: <Title>

## Overview

**PR:** <url>
**Issue:** <referenced issue url>
**Branch:** `<branch name>`
**Files Changed:** <count>
**Author:** @<username>

### Feature Summary
<1-3 sentence description of what the PR implements>

---

## Architecture

### Data Model
\`\`\`
<ASCII diagram of entities/relationships>
\`\`\`

### Component Structure
\`\`\`
<directory tree of new components>
\`\`\`

### New Files Summary
| Package | New Files | Purpose |
|---------|-----------|---------|
| api-core | X | <summary> |
| web-client | X | <summary> |
| api-contracts | X | <summary> |

---

## QA Issues Analysis

| # | Issue | Severity | Category | Status |
|---|-------|----------|----------|--------|
| 1 | <description> | P0/P1/P2 | <category> | Open/Fixed |

---

## Consistency Analysis

### ✅ Following Existing Patterns
<list of things done correctly>

### ⚠️ Consistency Issues Found

#### 1. <Issue Title>
**Location:** `<file path>`
**Problem:** <description>
**Existing Pattern:** <how it's done elsewhere>
**Fix:**
\`\`\`typescript
<code fix>
\`\`\`

---

## Recommendations

### P0 - Critical (Block Merge)
1. <issue with fix>

### P1 - High (Before Merge)
1. <issue with fix>

### P2 - Medium (Follow-up)
1. <issue>

---

## Files Changed Summary

### API Core (<count> files)
**New:**
- `<path>` - <purpose>

**Modified:**
- `<path>` - <changes>

### Web Client (<count> files)
**New:**
- `<path>` - <purpose>

**Modified:**
- `<path>` - <changes>

### API Contracts (<count> files)
- `<path>` - <purpose>

---

## Testing Recommendations

### Integration Tests
- [ ] <specific test scenario>

### E2E Tests
- [ ] <specific test scenario>

---

## Summary

<2-3 sentences with overall assessment and key recommendations>

**Recommendation:** Approve / Request Changes / Needs Discussion

---

*Review generated: <date>*

User: /review-pr 305

Claude:
1. Fetches PR #305 details (title, body, files, commits)
2. Fetches referenced issues from PR body
3. Parses scope: PrivatBank XLSX import, 47 files changed
4. Launches 10 PARALLEL skill-based review agents:
   - React Best Practices: Checks hooks, memoization, effects
   - React Native Best Practices: Checks performance, lists, animations
   - Composition Patterns: Checks component API design
   - Native UI Design: Checks navigation, styling, accessibility
   - Frontend Design: Checks visual hierarchy, theming
   - Vercel RN Skills: Checks platform-specific patterns
   - Expo Deployment: Checks EAS config, OTA updates
   - Expo Dev Client: Checks dev build, native modules
   - Native Data Fetching: Checks API calls, caching, offline
   - Expo Upgrade Compat: Checks SDK compatibility, deprecations
5. Merges and deduplicates issues from all agents
6. Categorizes: 2 P0, 5 P1, 8 P2
7. Creates gist with full analysis
8. Returns: https://gist.github.com/...

# Get PR review state
gh pr view <NUMBER> --json number,url,reviews --jq '{number, url, reviews: [.reviews[] | {author: .author.login, state: .state, body: .body}]}'

# Get all review comments (inline comments on code)
gh api repos/<OWNER>/<REPO>/pulls/<NUMBER>/comments

git add <changed files>
git commit -m "$(cat <<'EOF'
fix(<scope>): address PR review comments

- <summary of change 1>
- <summary of change 2>

Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
EOF
)"
git push

# Raw API call
gh api repos/owner/repo/pulls/123/comments

# Response includes both bot and human comments:
# - Copilot (bot): "Consider validating numeric fields..."
# - liaugust (human): "Enum instead"  <-- ADDRESS THIS
# - github-actions[bot]: "Coverage report..."

# Only address the human comment from liaugust

digraph address_review {
    rankdir=TB;
    node [shape=box];

    start [label="'Address review'" shape=ellipse];
    fetch [label="1. Fetch PR comments\ngh api .../pulls/N/comments"];
    filter [label="2. Filter human comments\n(ignore bots: Copilot, github-actions)"];
    parse [label="3. Parse each comment\n(file, line, body)"];

    subgraph cluster_fix {
        label="4. For each comment";
        style=dashed;
        read [label="Read file at path"];
        understand [label="Understand context"];
        implement [label="Implement fix"];
    }

    validate [label="5. Run validation\nyarn format && yarn ts && yarn lint"];
    commit [label="6. Commit & push"];
    done [label="Done" shape=ellipse];

    start -> fetch -> filter -> parse;
    parse -> read -> understand -> implement;
    implement -> validate -> commit -> done;
}