Proactive Review Workflow Skill
Automate multi-pass code review across quality, security, and performance dimensions.
Trigger Conditions
- PR opened or updated
- Merge event
- User invokes with "proactive review" or "full review"
Input Contract
- Required: PR diff or file changes
- Optional: Review focus areas, prior review comments
Output Contract
- Multi-dimensional review report (quality, security, performance)
- Categorized findings (blocking, suggestion, nit)
- Post-merge validation results
Tool Permissions
- Read: PR diffs, source code, test files, configs
- Write: Review comments, review reports
- Search: Related code and patterns
Execution Steps
- Analyze PR diff for scope and affected components
- Run quality pass (complexity, naming, error handling, dead code)
- Run security pass (injection, auth, secrets, dependencies)
- Run performance pass (N+1 queries, unbounded collections, missing indexes)
- Categorize findings: blocking (must fix), suggestion (consider), nit (style)
- Run post-merge validation on merged result
- Generate review report
Success Criteria
- All three dimensions reviewed (quality, security, performance)
- Findings categorized by severity
- No blocking findings remain unresolved
- Post-merge validation passes
Escalation Rules
- Escalate if PR is >400 lines (diminishing review quality)
- Escalate if Critical security finding detected
- Escalate if architectural drift detected
Example Invocations
Input: "Run proactive review on PR #42"
Output: Review: 3 files, 89 lines changed. Quality: 1 suggestion (extract helper function). Security: 1 blocking (SQL injection in search query — use parameterized query). Performance: 1 suggestion (add index for new WHERE clause). Post-merge: clean, no composition errors.
1---2name: proactive-review-workflow3description: Automate multi-pass code review across quality, security, and performance dimensions4---56# Proactive Review Workflow Skill78Automate multi-pass code review across quality, security, and performance dimensions.910## Trigger Conditions11- PR opened or updated12- Merge event13- User invokes with "proactive review" or "full review"1415## Input Contract16- **Required:** PR diff or file changes17- **Optional:** Review focus areas, prior review comments1819## Output Contract20- Multi-dimensional review report (quality, security, performance)21- Categorized findings (blocking, suggestion, nit)22- Post-merge validation results2324## Tool Permissions25- **Read:** PR diffs, source code, test files, configs26- **Write:** Review comments, review reports27- **Search:** Related code and patterns2829## Execution Steps301. Analyze PR diff for scope and affected components312. Run quality pass (complexity, naming, error handling, dead code)323. Run security pass (injection, auth, secrets, dependencies)334. Run performance pass (N+1 queries, unbounded collections, missing indexes)345. Categorize findings: blocking (must fix), suggestion (consider), nit (style)356. Run post-merge validation on merged result367. Generate review report3738## Success Criteria39- All three dimensions reviewed (quality, security, performance)40- Findings categorized by severity41- No blocking findings remain unresolved42- Post-merge validation passes4344## Escalation Rules45- Escalate if PR is >400 lines (diminishing review quality)46- Escalate if Critical security finding detected47- Escalate if architectural drift detected4849## Example Invocations5051**Input:** "Run proactive review on PR #42"5253**Output:** Review: 3 files, 89 lines changed. Quality: 1 suggestion (extract helper function). Security: 1 blocking (SQL injection in search query — use parameterized query). Performance: 1 suggestion (add index for new WHERE clause). Post-merge: clean, no composition errors.
diegosouzapw