Skip to content

refactor(cli): Use multi-agent parallel review in pr-review command #1286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yamadashy merged 3 commits into from
Mar 21, 2026
Merged

refactor(cli): Use multi-agent parallel review in pr-review command #1286

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
366159f
refactor(cli): Use multi-agent parallel review in pr-review command
yamadashy Mar 21, 2026
569e61a
fix(cli): Address review feedback on pr-review and review-loop commands
yamadashy Mar 21, 2026
d3aa21b
revert(cli): Remove redundant CLAUDE.md reference from conventions agent
yamadashy Mar 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 9 additions & 10 deletions .agents/commands/git/pr-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,20 +7,19 @@ $ARGUMENTS

If REPO and PR_NUMBER are not provided above, use `gh pr view` to detect the current PR.

Please review this pull request and provide feedback on:
- Code quality and best practices
- Potential bugs or issues
- Performance considerations
- Security concerns
- Test coverage
Spawn 6 agents in parallel, each reviewing the PR diff from a different angle:
- **Agent 1 — Code quality**: Bugs, logic errors, edge cases, code smells
- **Agent 2 — Security**: Vulnerabilities, injection risks, secret exposure, unsafe patterns
- **Agent 3 — Performance**: Inefficiencies, resource leaks, unnecessary allocations
- **Agent 4 — Test coverage**: Missing tests, untested edge cases, test quality
- **Agent 5 — Conventions**: Project conventions (.agents/rules/base.md), naming, structure
- **Agent 6 — Holistic review**: Overall design concerns, side effects, integration risks, and premortem analysis (potential failure scenarios, deployment risks)

Perform a premortem analysis: identify potential failure scenarios (e.g., edge cases, integration issues, deployment risks) and suggest mitigations.

Use the repository's CLAUDE.md for guidance on style and conventions. Be constructive and helpful in your feedback.
Each agent should only report noteworthy findings. After all agents report back, review their findings and keep only what you also deem noteworthy. Be constructive and helpful in your feedback.

## AI Bot Inline Comment Evaluation

Before starting your own review, evaluate existing AI bot inline review comments to reduce the maintainer's cognitive load:
Before spawning review agents, evaluate existing AI bot inline review comments to reduce the maintainer's cognitive load:

1. **Fetch inline review comments**:
```bash
Expand Down
Loading