sage-run-gauntlet

Launch parallel reviewer agents to analyze sage-lib diffs and consolidate feedback by severity.

26|3|Updated Sep 23, 2020
One-click install
npx skills add https://github.com/Kajabi/sage-lib --skill sage-run-gauntlet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sage-run-gauntlet
Source: https://github.com/Kajabi/sage-lib/tree/main/.claude/skills/sage-run-gauntlet
Command: npx skills add https://github.com/Kajabi/sage-lib --skill sage-run-gauntlet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launch parallel reviewer agents to validate sage-lib changes before PRs, reducing feedback cycles and catching issues early.

Core Features & Use Cases

  • Parallel reviewer execution: run code, design, a11y, and existence reviews simultaneously.
  • Severity-based consolidation: aggregate feedback into a single prioritized report.
  • Pre-PR governance: ideal for changes to components, tokens, or styles prior to developing PR.

Quick Start

Run the gauntlet on your current feature branch to generate a consolidated reviewer report.

Frequently Asked Questions about sage-run-gauntlet

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

FAQPage Schema
How do I run parallel code reviews before opening a PR?

To run parallel code reviews before a PR, execute the gauntlet on your feature branch to launch specialized reviewer agents simultaneously and consolidate their feedback by severity. This generates a single prioritized report for actionable feedback.

What is multi-agent code review and how does it work for component changes?

Multi-agent code review launches specialized agents like sage-code-reviewer, sage-design-reviewer, and sage-a11y-reviewer in parallel to analyze diffs. It consolidates feedback by severity to check code quality, token discipline, accessibility, and duplication across React components, SCSS, and design tokens.

Can I automate accessibility and design checks for React components and SCSS?

Yes, you can automate accessibility and design checks by running the gauntlet, which launches sage-a11y-reviewer and sage-design-reviewer agents in parallel to analyze your diffs and produce consolidated, severity-based feedback before you open a PR.

What's the best way to consolidate reviewer feedback by severity?

The best way to consolidate reviewer feedback by severity is to run parallel reviewer agents that analyze diffs and aggregate findings into a single prioritized report, ensuring actionable feedback is grouped by severity level for efficient pre-PR governance.

Does the gauntlet reviewer work with git workflows on a feature branch?

Yes, the gauntlet reviewer works with git workflows by analyzing diffs on your current feature branch against develop. It uses git workflows to launch parallel agents and produce a consolidated report before you open a PR.

When do I need to run parallel reviewer agents for sage-lib changes?

You need to run parallel reviewer agents for sage-lib changes before opening a PR against develop, specifically when modifying React components, SCSS files, or design tokens, to ensure code quality, token discipline, accessibility, and duplication checks are validated early.