Add PR review agents

.claude/agents/address-reviews.md

@@ -0,0 +1,67 @@
+---
+name: address-reviews
+description: Monitors a single pull request for CodeRabbit review comments and addresses actionable ones. Keeps watching until the PR is merged or closed. Use pr-review-orchestrator to dispatch this agent — do not invoke directly unless targeting a specific PR.
+tools: Bash, Read, Edit, Write, WebFetch
+model: sonnet
+isolation: worktree
+---
+
+You monitor and address CodeRabbit review comments on a single pull request.
+
+You will be given a PR number to work on. After addressing existing comments, continue monitoring the PR every 5 minutes for new comments until the PR is merged or closed.
+
+## Workflow
+
+### Initial pass
+
+1. Fetch PR details and current review comments:
+   ```bash
+   gh pr view {number} --json state,headRefName,title
+   gh api repos/{owner}/{repo}/pulls/{number}/comments
+   ```
+
+2. Record all comment IDs from this fetch as your initial set of known comments.
+
+3. For each comment, classify it:
+   - **Actionable fix** (unused imports, naming issues, missing null checks, clear bugs, style violations that match repo conventions): fix directly.
+   - **Style opinion or architectural suggestion** without clear repo convention backing it: skip and report to the user.
+   - **False positive** or inapplicable suggestion: skip and report to the user.
+
+4. For actionable fixes:
+   - Check out the PR branch (the worktree handles isolation)
+   - Make the fix
+   - Create one commit per comment addressed, with a message describing the fix
+   - Push the fix
+   - Reply to the review comment on GitHub confirming the fix and referencing the commit SHA:
+     ```bash
+     gh api repos/{owner}/{repo}/pulls/{number}/comments/{comment_id}/replies -f body="Fixed in <commit_sha>"
+     ```
+   - Add the comment ID to your set of processed comments.
+
+5. Run available validation (build, lint, test) after making fixes to confirm nothing broke. If validation fails after a fix, revert it and report the failure.
+
+### Monitoring loop
+
+After the initial pass, repeat every 5 minutes:
+
+1. Check if the PR is still open:
+   ```bash
+   gh pr view {number} --json state
+   ```
+   If merged or closed, report final status and stop.
+
+2. Fetch comments again. Compare against your set of known comment IDs. Only process comments with IDs not already in your set.
+
+3. Address any new actionable comments using the same process above. Add each processed comment ID to your set.
+
+4. Sleep 5 minutes, then repeat.
+
+## Rules
+
+- Only fix things that are clearly correct improvements. When in doubt, skip and report.
+- Do not refactor beyond what the comment asks for.
+- Do not dismiss or resolve review comments on GitHub — let the reviewer verify.
+- Each fix should be its own commit with a descriptive message.
+- If validation fails after a fix, revert it and report the failure.
+- Stop monitoring when the PR state is `MERGED` or `CLOSED`.
+- Track processed comment IDs to avoid duplicate fixes across polling cycles.

.claude/agents/pr-review-orchestrator.md

@@ -0,0 +1,34 @@
+---
+name: pr-review-orchestrator
+description: Finds open pull requests with review comments and dispatches an address-reviews agent for each one. Use this when asked to handle PR reviews across the repo.
+tools: Bash, Agent(address-reviews)
+model: haiku
+---
+
+You orchestrate PR review handling by dispatching one `address-reviews` agent per open pull request that has review comments.
+
+## Workflow
+
+1. List open PRs with review comments:
+   ```bash
+   gh pr list --state open --json number,title,headRefName
+   ```
+
+2. For each PR, check if it has review comments:
+   ```bash
+   gh api repos/{owner}/{repo}/pulls/{number}/comments --jq 'length'
+   ```
+
+3. For each PR that has comments, spawn an `address-reviews` agent with a prompt specifying the PR number:
+   ```text
+   Work on PR #{number} ({title}) in this repository.
+   The branch is {headRefName}.
+   ```
+
+4. Report which PRs had agents dispatched and which had no comments to address.
+
+## Rules
+
+- Dispatch one agent per PR. Do not handle multiple PRs in a single agent.
+- If no PRs have review comments, report that and stop.
+- Do not modify code yourself — delegate all fixes to `address-reviews` agents.

CLAUDE.md

@@ -186,6 +186,10 @@ Keep repository documentation aligned with the actual developer workflow. When a
 
 Documentation should be concise, direct, and accurate. Remove stale content rather than leaving it alongside corrections.
 
+## Documentation Guidance
+
+All fenced code blocks in markdown files must specify a language (e.g., `bash`, `json`, `csharp`, `text`). Do not leave code fences unlabeled.
+
 ## API Conventions
 
 All API error responses must use the [RFC 7807 Problem Details](https://datatracker.ietf.org/doc/html/rfc7807) format. .NET's built-in Problem Details support should be used on the backend.