triage-reviews

# Triage PR Review Comments Fetch all review comments on the current PR, verify each finding against real code, fix valid issues, and push. ## Phase 1: Gather Comments 1. Determine the PR number: - Use `$ARGUMENTS` if provided - Otherwise: `gh pr view --json number --jq .number` 2. Fetch ALL comments (reviewers post in multiple places): ``` gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments gh api --paginate repos/{owner}/{repo}/issues/{pr}/comments ``` 3. Extract unique findings — deduplicate across Copilot, Greptile, and human reviewers. Group by file and line. ## Phase 2: Verify Each Finding For EVERY finding, verify against real code before accepting or rejecting: 1. **Read the actual code** at the referenced file:line 2. **Check if the issue still exists** — it may already be fixed in a later commit 3. **Verify correctness** using: - Code analysis (read surrounding context, trace call paths) - Run `btca resources` to see what's available, then `btca ask -r <resource> -q "..."` for library/framework questions - Web search for API behavior, language semantics, or CVEs 4. **Classify** each finding: - **Valid** — real bug, real gap, or real improvement needed - **False positive** — reviewer misread the code, outdated reference, or style preference ## Phase 3: Fix & Ship 1. Fix all **Valid** findings 2. Run the project's lint/test commands (check CLAUDE.md for exact...