Awesome-omni-skill Proactive Review Workflow
Automate multi-pass code review across quality, security, and performance dimensions
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/proactive-review-workflow" ~/.claude/skills/diegosouzapw-awesome-omni-skill-proactive-review-workflow && rm -rf "$T"
manifest:
skills/development/proactive-review-workflow/SKILL.mdsource content
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.