summon-team-review

Orchestrate parallel reviews from Checker, Legal, Gal, and GitDude roles.

7|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Nate-Vish/Auto-Mates --skill summon-team-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summon-team-review
Source: https://github.com/Nate-Vish/Auto-Mates/tree/main/.claude/skills/summon-team-review
Command: npx skills add https://github.com/Nate-Vish/Auto-Mates --skill summon-team-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate parallel reviews from dedicated roles (Checker, Legal, Gal, GitDude) to assess a target artifact for quality, security, compliance, and user impact.

Core Features & Use Cases

  • Spawn four reviewers to evaluate code quality, compliance, UX, and release readiness.
  • Coordinate parallel reviews with clear deliverables stored in Dashboard/Work_Space.
  • Apply to code, docs, or agent identities and produce multi-perspective verdicts.

Quick Start

Invoke the skill with /summon-team-review <target> to start a four-person review team.

Frequently Asked Questions about summon-team-review

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

FAQPage Schema
How do I run a coordinated team review for code quality and compliance?

A coordinated team review spawns multiple dedicated roles to evaluate a target artifact in parallel. This approach assigns reviewers to assess code quality, security, compliance, and user impact, then aggregates their structured feedback into actionable verdicts.

Can I review documentation and agent identities, or is it limited to source code?

You can review documentation and agent identities, not just source code. The team review process applies to codebases, documentation, or agent identities across a project, guiding diverse review workflows to deliver multi-perspective quality and compliance verdicts.

What is the best way to assess release readiness across multiple review roles?

Assessing release readiness across multiple roles requires orchestrating parallel reviews from dedicated perspectives like quality checkers, legal, and UX reviewers. This generates clear deliverables and structured outputs, recording actionable items for release management.

How do I start a multi-perspective security and UX review?

Start a multi-perspective security and UX review by invoking the skill with your target artifact. This spawns a four-person review team to evaluate quality, compliance, release readiness, and user impact, storing structured feedback in a workspace.

Does parallel code review work without external dependencies?

Parallel code review works without external dependencies. The orchestration logic internally coordinates dedicated review roles, creates structured outputs in a dashboard or workspace, and records verdicts autonomously.

When should I not use a multi-role code review approach?

Avoid using a multi-role code review approach for simple, single-perspective checks that do not require compliance, legal, or UX validation. It is designed for complex artifacts needing coordinated quality, security, and release readiness assessments.