stamina

Dispatch artifacts through multiple review skills and aggregate verdicts.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill stamina
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stamina
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/stamina
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill stamina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fan-out review adapter. Routes a high-blast-radius artifact (plan or PR) through multiple heterogeneous review passes and gates on consensus. Does not review; dispatches existing review skills (/simplify, /review, /review-senior, /safer:dogfood, /codex, /security-review for PRs; /safer:dogfood + /safer:review-senior + /codex for plans) and aggregates their verdicts. N is set by the blast-radius x reversibility table in PRINCIPLES.md > Durability. Two invocation modes: --plan <sub-issue URL> and --pr <pr URL>. Use when the caller (typically /safer:orchestrate Phase 5c) has decided the artifact warrants stamina. Do NOT self-invoke from the working modality; that is Principle 5 self-polishing.

Core Features & Use Cases

  • Dispatch a heterogeneous set of reviewers across multiple skills to evaluate an artifact.
  • Aggregate verdicts into a single consolidated result and publish it to the artifact thread.
  • Support two invocation modes (--plan and --pr) and enforce the independence constraint (no same skill+model twice in a dispatch).
  • Read verdicts from GitHub, not internal agent output, and optionally transition workflow labels.

Quick Start

Invoke stamina with --plan or --pr and allow it to fan out reviewers according to the blast-radius rules.

Frequently Asked Questions about stamina

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

FAQPage Schema
How do I orchestrate multiple reviewer passes for a GitHub pull request?

You can gate consensus across multiple heterogeneous review passes by dispatching diverse review skills and aggregating their verdicts from GitHub. The adapter supports two invocation modes, --plan and --pr, to route artifacts through multiple independent reviewers.

How does consensus gating work for automated code review?

Consensus gating aggregates per-reviewer verdicts read directly from GitHub into a single consolidated result. The dispatcher enforces independence by preventing any repeated skill and model combination across the heterogeneous review passes.

When do I need to fan out review skills for a high-blast-radius artifact?

You need to fan out review skills when a caller decides an artifact warrants stamina based on the blast-radius and reversibility table. It is explicitly designed for high-blast-radius artifacts like plans or PRs that require durable consensus.

Can I use a dispatcher to route a plan through multiple senior review passes?

Yes, you can route a plan through multiple review passes by invoking the adapter with the --plan flag and a sub-issue URL. The dispatcher routes plans through skills like /safer:dogfood, /safer:review-senior, and /codex, aggregating their verdicts.

What are the limitations of using a fan-out review dispatcher?

A key limitation is that the dispatcher does not review artifacts itself; it only aggregates existing review skills. Additionally, you should not self-invoke the adapter from the working modality, as that violates the self-polishing principle.