review-prlisted

# Review a Pull Request Generate a thorough code review for a pull request, structured with severity levels. ## Tools Needed - `Bash` — `gh pr view`, `gh pr diff`, and `gh api` for GitHub access - `Read` — read queue items, config, and local repo files - `Write` — write draft review - `Grep`, `Glob` — search codebase for patterns ## Input Either: - A queue item file path in `~/.local/share/engineer-agent/queue/incoming/` with type `pr-review` - Or a direct PR URL/reference (owner, repo, PR number) ## Steps ### 1. Load PR Details If working from a queue item, read the file to get `repo`, `pr_number`, and `project` from frontmatter. Read `~/.local/share/engineer-agent/engineer.yaml` to access project config at `projects.<project>` if needed. Fetch PR details and diff via Bash: ```bash gh pr view {pr_number} --repo {repo} --json title,body,author,files,commits,headRefName,baseRefName,url,number gh pr diff {pr_number} --repo {repo} ``` This gives you: - Full diff (from `gh pr diff`) - PR description, files changed list, and commit messages (from `gh pr view --json`) ### 2. Understand Team Conventions Try to read the target repo's `CLAUDE.md`. If the project has a `path` in config (`projects.<project>.path`), use `Read` to read `{path}/CLAUDE.md` directly. For remote repos, fetch via Bash: ```bash gh api repos/{owner}/{repo}/contents/CLAUDE.md --jq '.content' | base64 -d ``` This file contains: - Architecture guidelines - Past team decisions - Code style conventions