roster-qa

Run ordered build, test, lint, and project checks with GO/NO-GO verdicts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual QA is inconsistent, often misses critical quality gates, and fails to integrate with staged development pipelines, leading to avoidable regressions and blocked shipping workflows. This Skill enforces standardized, deterministic quality checks that align with the roster pipeline's workflow, ensuring no step is skipped and all issues are caught before code proceeds.

Core Features & Use Cases

  • Ordered Quality Gates: Automatically runs build, full test suite, linting, and project-specific checks in a fixed order, stopping immediately if any gate fails to avoid wasting time on downstream checks.
  • Standardized Verdicts: Produces a machine-readable GO/NO-GO verdict that integrates directly with the roster pipeline's /roster-ship and /roster-implement commands, with full raw error logs for NO-GO outcomes.
  • Cross-Runtime & TUI Validation: Automatically re-runs checks on a secondary runtime if available to catch runtime-specific issues, and validates TUI interfaces via tmux matrix testing for applications with graphical components.
  • Use Case: A development team using the roster pipeline to implement a new authentication feature can use this Skill to automatically run all required quality checks after implementation and review, getting a clear pass/fail result that either triggers shipping or sends work back to implementation with exact error details.

Quick Start

Use the roster-qa skill to run all required quality gates for the current pipeline task and receive a GO or NO-GO verdict with detailed error logs if any checks fail.

Frequently Asked Questions about roster-qa

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

FAQPage Schema
How do I enforce deterministic quality gates in a software development pipeline?

Deterministic quality gates enforce standardized checks like build verification, test suite execution, and linting in a fixed order. This eliminates inconsistent manual QA by stopping immediately upon failure and producing standardized GO/NO-GO verdicts with detailed error logs.

What is a GO/NO-GO verdict in pipeline QA and how does it work?

A GO/NO-GO verdict is a machine-readable pass or fail result generated after running ordered quality gates. It integrates directly with pipeline shipping and implementation commands, appending audit trail events to the task state ledger and providing raw error logs for any NO-GO outcome.

How do I run automated cross-runtime checks and TUI validation for pipeline tasks?

Automated cross-runtime checks re-run build, test, and linting gates on a secondary runtime to catch environment-specific issues. TUI validation uses tmux matrix testing to verify graphical interfaces, ensuring comprehensive quality coverage before issuing a final GO/NO-GO verdict.

Does the roster pipeline support automatic error logging when quality gates fail?

Yes, when quality gates fail during the post-implementation or post-review stages, the pipeline generates a NO-GO verdict with full raw error logs. This sends work back to the implementation phase with exact error details and records the event in the task state ledger.

What's the best way to standardize QA checks across multiple pipeline stages?

Standardizing QA checks requires applying ordered quality gates across post-implementation and post-review stages. By executing build verification, full test suites, linting, and project-specific checks sequentially, the pipeline ensures no step is skipped and issues are caught before code proceeds to shipping.