review-work

Coordinate parallel subagent reviews of code, security, performance, and tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nxy7/streampai-elixir --skill review-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-work
Source: https://github.com/nxy7/streampai-elixir/tree/main/.claude/skills/review-work
Command: npx skills add https://github.com/nxy7/streampai-elixir --skill review-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates parallel, multi-specialist reviews of code and project changes by deploying independent subagents to analyze code quality, security, performance, and test coverage.

Core Features & Use Cases

  • Phase-based analysis: assign 4–6 specialist roles and run parallel reviews, including a Codex Fresh Eyes perspective.
  • Cross-pollination & synthesis: consolidate findings across specialists to identify overlaps, gaps, and systemic risks.
  • Actionable reporting: output prioritized issues with file:line references and concrete remediation steps.

Quick Start

Use the review-work-agent to initiate a structured multi-agent review for a target area or file.

Frequently Asked Questions about review-work

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

FAQPage Schema
How do I automate multi-agent code review for git changes?▼

Automated multi-agent code review deploys independent subagents to analyze code quality, security, performance, and test coverage in parallel. It coordinates these specialist perspectives to consolidate findings and produce a prioritized, actionable report with file:line references.

Can I run parallel security and performance analysis on my repository?▼

Parallel security and performance analysis assigns specialist roles to independent subagents, enabling concurrent reviews of your repository changes. This cross-pollination approach identifies overlaps, gaps, and systemic risks across code, documentation, and configuration adjustments.

What do I need to set up multi-specialist git analysis?▼

Multi-specialist git analysis requires git context and an agent orchestration tool to spawn subagents. These prerequisites allow the system to deploy independent agents, aggregate their findings, and generate a convergent, prioritized report.

Does automated code review work for documentation and configuration updates?▼

Automated code review is applicable to documentation updates and configuration adjustments across a repository, not just code changes. It analyzes these modifications using the same parallel, multi-specialist subagent deployment and consolidated reporting mechanism.

What is the best way to consolidate findings from parallel code reviews?▼

The best way to consolidate parallel code review findings is through cross-pollination and synthesis. This mechanism identifies overlaps and systemic risks across specialist analyses, outputting prioritized issues with concrete remediation steps and file:line references.

Why use subagents for code review instead of a single agent?▼

Using subagents for code review enables phase-based analysis with 4-6 specialist roles, including a Codex Fresh Eyes perspective. This parallel deployment prevents single-agent bottlenecks and allows independent analysis before consolidating findings into an actionable report.