Windsurf rules

1---
2name: respond-review
3model: sonnet
4description: "Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings."
5---
6 
7# Respond Review
8> **HARD GATE** — **HARD GATE** — Every reviewer comment must be addressed (fix, disagree + document reason, or ask clarification). Do NOT ignore feedback and merge.
9 
10 
11Work through reviewer findings systematically. Don't apply changes blindly — categorize first, then decide, then fix, then verify.
12 
13## Process
14 
15### 1. Read the full review report
16 
17Read every finding before acting on any of them. Get the full picture first.
18 
19### 2. Categorize findings
20 
21For each finding, assign a category:
22 
23| Category | Meaning | Action |
24|----------|---------|--------|
25| **must-fix** | Correctness bug, security issue, test failure, CONVENTIONS.md violation | Fix before proceeding |
26| **should-fix** | Code quality issue, naming, clarity — worth fixing but not blocking | Fix if time allows |
27| **consider** | Architectural suggestion, alternative approach — may or may not apply | Discuss with user |
28 
29Create a numbered list of all findings with their categories.
30 
31### 3. Confirm with user (for consider-category items)
32 
33For each "consider" item, briefly describe the trade-off and ask: "Apply, skip, or discuss?"
34 
35### 4. Apply must-fix items first
36 
37Fix every must-fix item. For each one:
38- Describe what you're changing and why
39- Make the change
40- Run the verify command if one exists for this area
41 
42### 5. Apply should-fix items
43 
44Apply should-fix items. If any are large enough to warrant their own commit, note them separately.
45 
46### 6. Run the full suite
47 
48After all changes are applied:
49 
50```bash
51<full test command>
52<typecheck command>
53<lint command>
54```
55 
56- [ ] All tests pass
57- [ ] No type errors
58- [ ] No lint violations
59 
60### 7. Report
61 
62Summarize what was applied and what was skipped:
63 
64```
65Applied (must-fix): #1, #2, #3
66Applied (should-fix): #4
67Skipped (consider): #5 — agreed with user to defer
68All tests pass.
69```
70 
71Suggest next skill: `commit-message`.
72