c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.6 KiB
1.6 KiB
Review a pull request by number: fetch the diff, analyze changes, and post review comments.
Steps
- Fetch PR details:
gh pr view <number> --json title,body,files,additions,deletions,commits. - Get the full diff:
gh pr diff <number>. - Read the PR description and any linked issues for context.
- Analyze each changed file across dimensions:
- Correctness: Logic errors, edge cases, missing error handling.
- Security: Input validation, credential exposure, injection risks.
- Performance: N+1 queries, unnecessary allocations, missing caching.
- Design: Coupling, naming, abstraction level, API surface.
- Tests: Coverage of new code paths, edge case testing.
- Check that CI checks are passing:
gh pr checks <number>. - Classify findings as CRITICAL, WARNING, or SUGGESTION.
- Present the review summary and offer to post it as a PR review comment.
- If approved, submit:
gh pr review <number> --approve --body "<summary>".
Format
## PR Review: #<number> - <title>
### Critical
- [ ] file.ts:L42 - Description of critical issue
### Warnings
- [ ] file.ts:L15 - Description of warning
### Suggestions
- [ ] file.ts:L88 - Description of suggestion
### Summary
Overall assessment and recommendation (approve/request-changes).
Rules
- Review the full diff, not just the latest commit.
- Be specific with line references and provide concrete fix suggestions.
- Limit findings to the 15 most impactful to reduce noise.
- Acknowledge well-written code sections briefly.
- Never auto-approve PRs with critical findings.