sworm-review

Identifies Sworm change issues via adversarial seven-agent swarm workflow with hard gates and severity-ranked findings tables.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/TophC7/Sworm --skill sworm-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sworm-review
Source: https://github.com/TophC7/Sworm/tree/main/.claude/skills/sworm-review
Command: npx skills add https://github.com/TophC7/Sworm --skill sworm-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables targeted adversarial review of Sworm changes to surface realism-based issues that threaten correctness, maintainability, and architectural coherence.

Core Features & Use Cases

  • Structured seven-agent swarm workflow to inspect changes for architectural fit, pattern reuse, and UI consistency.
  • Hard Gate checks that require reading AGENTS.md and SKILL.md guidance before findings to ensure aligned standards.
  • Consolidated findings with severity-ranked issues and actionable fixes for PRs, staged changes, or design decisions.
  • Supports precise repo reads to maximize signal while minimizing scope.

Quick Start

Run the sworm-review skill on the target change set to surface architecture, design, and style issues.

Frequently Asked Questions about sworm-review

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

FAQPage Schema
How do I run an adversarial code review for Svelte 5 and Rust changes?

Perform an adversarial code review using a seven-agent swarm to inspect Svelte 5 and Rust changes. The workflow applies hard gates and targeted repo reads to surface architectural, UI consistency, and correctness issues.

What is a protocol-driven swarm workflow for code review?

A protocol-driven swarm workflow uses seven specialized agents to evaluate code changes against architectural standards. It enforces hard gate checks requiring AGENTS.md and SKILL.md reads before producing severity-ranked findings tables.

Can I review staged diffs and design decisions across Tauri boundaries?

Yes, you can review staged diffs, PRs, and design decisions across Tauri and Rust boundaries. The review targets architectural fit, pattern reuse, and UI consistency across these specific framework boundaries.

How do I ensure UI pattern reuse is checked during a pull request review?

Ensure UI pattern reuse is checked by applying a codebase-aware review that reads existing repository guidance. The swarm workflow specifically inspects changes for pattern reuse and UI consistency before generating actionable fixes.

What are the limitations of using an adversarial swarm for codebase-aware review?

The adversarial swarm review requires reading AGENTS.md and SKILL.md guidance to pass hard gates, meaning it cannot bypass protocol checks. It focuses on maximizing signal through targeted repo reads rather than scanning the entire codebase.