review-swarm

Orchestrate parallel read-only git diff reviews with four sub-agents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tomrford/dotfiles --skill review-swarm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-swarm
Source: https://github.com/tomrford/dotfiles/tree/main/.agents/skills/review-swarm
Command: npx skills add https://github.com/tomrford/dotfiles --skill review-swarm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates four read-only sub-agents to review a current git diff or explicit file scope in parallel, surfacing high-signal issues (behavior regressions, security or privacy risks, performance or reliability concerns, and coverage gaps) without editing files, enabling faster triage for changes.

Core Features & Use Cases

  • Parallel, read-only review of diffs with four specialized sub-agents.
  • Centralized synthesis that filters, orders, and summarizes only the most impactful findings.
  • Safe pre-merge evaluation: no file changes are committed by any agent.

Quick Start

Invoke the Review Swarm on the active diff to receive a concise, prioritized issue summary.

Frequently Asked Questions about review-swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a parallel code review on my current git diff?

You can review specific file scopes by explicitly providing them to the Skill. It applies its parallel sub-agents to the requested files instead of the active git diff, producing actionable findings.

Does read-only code review modify my files?

The Skill surfaces high-signal issues including behavior regressions, security or privacy risks, performance or reliability concerns, and coverage gaps, filtering and ordering them by impact.

How do I get a prioritized summary of security risks in my code changes?

To get a prioritized summary of security risks in your code changes, the Skill's centralized synthesis filters and orders findings from its parallel review, providing structured summaries with confidence ratings and a concise path forward.

Can I analyze an explicit file scope instead of the active git diff?

Yes, you can analyze an explicit file scope instead of the active git diff. The Skill applies its parallel review to requested files or diffs, producing actionable findings regardless of the input scope.

What is the best way to evaluate code changes before merging without editing files?

The best way to evaluate code changes before merging without editing files is using a parallel, read-only diff review. This Skill coordinates specialized sub-agents to surface high-priority issues and risks safely.