roster-review

Apply mechanical code fixes and generate GO/NO-GO JSON verdicts for pipeline reviews.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill roster-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roster-review
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/roster-review
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill roster-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured, inconsistent code reviews lead to missed critical issues, wasted time on trivial fixes, and unclear pass/fail decisions that block pipeline progression. This skill eliminates those gaps by standardizing the review process with automatic mechanical fixes and evidence-based verdicts.

Core Features & Use Cases

  • Fix-first automated corrections: Automatically resolves trivial issues like dead code, magic numbers, stale comments, and style inconsistencies without human intervention, only escalating ambiguous or high-impact changes.
  • Conditional specialist review: Invokes relevant specialists (spec compliance, code quality auditor, architect, cross-runtime reviewer) based on diff scope, task mode (Express/Fast/Full), and available knowledge bases or cross-runtime CLIs.
  • Structured pipeline verdicts: Generates a standardized JSON review output with GO/NO-GO status, categorized findings, and escalation flags to integrate directly with the Roster pipeline, routing work to QA, shipping, or implementation as needed. Use case: A software team using the Roster agent pipeline can use this skill to standardize post-implementation reviews, ensure consistent quality gates across all tasks, and automatically route work based on clear, evidence-based criteria instead of ad-hoc human judgment.

Quick Start

Use the roster-review skill to conduct a structured fix-first review of the completed implementation for the current task and generate a GO/NO-GO verdict for pipeline progression.

Frequently Asked Questions about roster-review

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

FAQPage Schema
How do I automate trivial code fixes during a pipeline review?

Automated code review applies mechanical corrections for trivial issues like dead code, magic numbers, and stale comments without human intervention, escalating only ambiguous or high-impact changes to specialists.

What is a GO/NO-GO verdict in a development pipeline?

A GO/NO-GO verdict is a standardized pipeline progression decision output as structured JSON, categorizing findings and setting escalation flags to route work to QA, shipping, or implementation.

How do I standardize post-implementation code reviews across multiple agents?

Standardized post-implementation reviews use conditional specialist invocation based on diff scope, task mode, and available knowledge bases to ensure consistent quality gates across coordinated agent workflows.

Does automated code review support cross-runtime environments?

Cross-runtime review is supported conditionally by invoking a cross-runtime reviewer specialist based on the available cross-runtime CLIs and the specific scope of the code diff.

When should I use a fix-first review approach for code quality?

Use fix-first review when you need to eliminate unstructured reviews and automatically resolve style inconsistencies, ensuring only critical issues and high-impact changes block pipeline progression.

Can I use structured JSON verdicts to gate my software deployment pipeline?

Yes, structured JSON verdicts provide a GO/NO-GO status with categorized findings and escalation flags designed to integrate directly with development pipelines for routing work.