agent-code-review-swarm_skill

This skill orchestrates a multi-agent code review swarm to identify security, performance, and architectural issues across PRs.
  • TypeScript

14.1k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ruvnet/ruflo --skill agent-code-review-swarm

  • SKILL.md11.9 KB

Overview

This skill deploys a coordinated swarm of specialized AI agents to perform automated, context-aware code reviews that go beyond static analysis. It runs multiple reviewers (security, performance, style, architecture, accessibility) in parallel, aggregates findings, and posts actionable comments and quality-gate results back to your CI or pull request. The goal is faster, more consistent reviews and fewer regressions in production.

How this skill works

The skill initializes a multi-agent review session with PR context (diff, changed files, history) and spawns dedicated agents for security, performance, style, architecture, etc. Each agent runs targeted checks, suggests fixes, and assigns severity. An orchestrator aggregates results, applies configurable thresholds and quality gates, and posts inline comments, review statuses, or requests changes through the repository CLI or CI integration.

When to use it

  • On pull requests where multiple risk domains must be evaluated (security, perf, style, architecture)
  • For large or high-risk PRs that need comprehensive, parallelized review coverage
  • When you want automated, consistent enforcement of team coding standards and security rules
  • As part of CI pipelines to gate merges with measurable quality thresholds
  • To batch-analyze related PRs for integration and cross-change consistency

Best practices

  • Define clear review rules and thresholds (block vs warn vs suggest) in repo config
  • Limit agents per run to balance depth and latency for routine PRs; increase depth for critical paths
  • Provide examples and documentation for suggested fixes to reduce back-and-forth
  • Use incremental reviews and caching for large codebases to speed repeat runs
  • Treat agent findings as actionable suggestions; triage and tune models to reduce false positives

Example use cases

  • Security-critical change to authentication or payment code: run comprehensive security + architecture agents and require approval before merge
  • Performance optimization PR: spawn performance, database and benchmarking agents to compare against baseline and suggest optimizations
  • UI component library changes: run accessibility, style, i18n and visual-regression agents and post contextual inline comments
  • Batch analysis for a release: analyze multiple PRs together to detect cross-PR conflicts and integration risks
  • Automated CI gate: fail merges when security agent flags critical issues or when performance regressions exceed thresholds

FAQ

Yes. Configure path-based triggers to select agents and depth per file patterns so only relevant specialists run.

How are critical findings enforced?

The orchestrator applies configured quality gates and can block merges, request changes, or add labels based on severity rules.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
agent-code-review-swarm skill by ruvnet/ruflo | VeilStrat