← ClaudeAtlas

pr-reviewlisted

Review a GitHub PR by analyzing the branch diff against the linked issue requirements, launch parallel analysis agents (context + security), then post structured findings as PR comments.
open-ace/open-ace · ★ 4 · Code & Development · score 73
Install: claude install-skill open-ace/open-ace
# PR Review Workflow ## 1. Gather context ```bash # Get issue details (if PR references an issue) gh issue view <issue-number> --repo <owner>/<repo> --json title,body,author,labels,state,comments # Get PR details gh pr view <pr-number> --repo <owner>/<repo> --json title,body,headRefName,baseRefName,state,comments # See what changed git diff main...HEAD --stat git diff main...HEAD --name-only git log main...HEAD --oneline ``` ## 2. Read full diff and each changed file ```bash git diff main...HEAD ``` Then use `read_file` to read surrounding context in each changed file — not just the diff hunks, but the functions/classes they belong to. This reveals edge cases the diff alone cannot show. ## 3. Launch parallel analysis agents Launch background agents simultaneously for deeper analysis while you continue reading code: - **Context agent**: Trace variable origins, function signatures, table schemas, and call chains for each changed area. Specifically trace where untrusted input (request body, query params) flows. - **Security agent (attacker mindset)**: For every change, ask "what can an unauthenticated or malicious caller do with this?" Check auth decorators, trust boundaries, error handling paths that silently swallow failures. - **Cross-cutting agent** (if needed): Grep for new identifiers (stream types, event names, table columns) to verify they're consumed correctly everywhere. **Critical**: Do NOT consider the review complete until every agent's findings are poste