chore: replace review subagents with warden (#151)

Author: gricha

.claude/agents/perf-review.md

@@ -45,28 +45,14 @@ That's it. No "Test Plan", no "Screenshots", no checklists unless truly needed.
    git diff --name-only main...HEAD
    ```
 
-2. **Run code-simplifier first** (if available):
-
-   Run the `code-simplifier:code-simplifier` agent to simplify and clean up the code.
-   This step modifies code, so it must run before reviews. Commit any changes it makes.
-
-3. **Run validation + reviews in parallel**:
-
-   After code-simplifier is done, run these concurrently:
-   - `bun run validate` (background)
-   - Review agents based on changed files:
-
-   | Changed files | Agent to spawn |
-   |---------------|----------------|
-   | `src/agent/`, auth, user input, data handling | `security-review` |
-   | Loops, data fetching, DB queries, heavy computation | `perf-review` |
-   | `web/` or `mobile/` (.tsx/.jsx files) | `react-review` |
-
-   Spawn all applicable review agents in parallel using the Task tool.
+2. **Run validation**:
+   ```bash
+   bun run validate
+   ```
 
-4. **Fix any issues** found by validation or review agents before proceeding
+3. **Fix any issues** found by validation before proceeding
 
-5. **Create PR** (only after validation passes and reviews are addressed):
+4. **Create PR** (only after validation passes):
    ```bash
    gh pr create --title "<type>: <description>" --body "$(cat <<'EOF'
    ## Summary

.claude/agents/react-review.md

@@ -49,17 +49,11 @@ Run the appropriate validation for your changes.
 
 3. If validation fails, fix issues and re-run
 
-## Run Review Agents in Parallel
-
-While validation runs, spawn review subagents in parallel based on what changed:
-
-| Changed files | Run agent |
-|---------------|-----------|
-| Auth, user input, data handling | `security-review` |
-| Loops, data fetching, DB queries | `perf-review` |
-| `web/` or `mobile/` (.tsx/.jsx) | `react-review` |
-
-These agents review your local changes and report issues. Run them in parallel with validation to save time.
+4. Run warden to get code review feedback locally (security, react best practices, code simplification):
+   ```bash
+   warden -v
+   ```
+   The `-v` flag streams findings in real-time. Fix any issues warden finds before creating a PR.
 
 ## Notes
 

.claude/agents/security-review.md

@@ -13,19 +13,9 @@ Use the `skill` tool for common workflows:
 
 If validation fails due to missing tools, install dependencies first with `bun install`.
 
-## Code Review Agents
+## Code Review
 
-Before submitting changes, run review agents in parallel with validation:
-
-| Agent | When to use |
-|-------|-------------|
-| `security-review` | After auth, data handling, or user input changes |
-| `perf-review` | After adding loops, data fetching, or heavy computation |
-| `react-review` | After React component changes (web/ or mobile/) |
-
-These agents review your local changes (uncommitted, branch diff, or last commit) and report issues. They will be honest - if the code is good, they'll say so. They may also suggest lint rules or tests to prevent similar issues in the future.
-
-**Location**: Claude Code uses `.claude/agents/`, OpenCode uses `.opencode/agent/` (OpenCode agents reference the Claude Code files for shared instructions).
+Code reviews (security, react best practices, code simplification) are handled automatically by [Warden](https://github.com/getsentry/warden) on pull requests. See `warden.toml` for the configured triggers.
 
 ## Architecture