Coordinate parallel specialist code reviews and aggregate findings into unified reports.
npx skills add https://github.com/duronext/jig --skill review-duronext
Please help me install this Agent Skill. Skill: review Source: https://github.com/duronext/jig/tree/main/core/skills/review Command: npx skills add https://github.com/duronext/jig --skill review-duronext
Coordinating code reviews across multiple specialists can be slow and brittle; this Skill streamlines pre-PR and quality-gate reviews by dispatching a swarm of focused reviewers and aggregating their findings into a single report.
Invoke /review during a code review to start the swarm-driven evaluation.
High-intent search queries and answers about installing and using this skill.
Parallel code reviews with a swarm of specialists are dispatched by invoking /review during your pre-PR verification. The swarm concurrently evaluates security, correctness, and performance, then aggregates findings into a single unified report to guide remediation.
Configuration-driven discovery is the mechanism that automatically identifies and selects tier-based specialist reviewers for the code-review swarm. It enforces consistent participation across focused domains and outputs a unified set of actionable findings.
Yes, automated code review integrates directly into team-dev quality gates and pre-PR checks. Invoking /review dispatches the specialist swarm to enforce thorough, consistent verification and produces a unified report for faster decisions.
Yes, parallel review operates with zero external dependencies or components. It internally manages the configuration-driven discovery, tier-based participation, and automated aggregation required to dispatch the specialist swarm and report findings.
The best way to aggregate code review findings is dispatching a parallel specialist swarm via /review. It automates the aggregation of security, correctness, and performance findings into a single unified report, accelerating pre-PR remediation decisions.
You should avoid a parallel swarm for pre-PR code review if your changes are trivial and do not warrant multi-specialist verification across security, correctness, and performance, as dispatching tier-based reviewers adds overhead for minimal remediation value.
fyrsmithlabsOrchestrate parallel multi-agent code reviews with adaptive budgets and consolidated reports.
thimsluggaApply iproute2 patch verification criteria and generate PASS/FAIL reports.
maluradityaValidate builds and reviews, then apply a chosen merge workflow to finish a development branch.
atelier-fashionEvaluate recent code changes with a five-agent pre-push review.
