roster-doctor

Verify roster installation integrity and development environment runnability before pipeline runs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting roster pipeline work with a broken installation or non-functional development environment leads to wasted time, failed execution batches, and avoidable rework. This Skill eliminates that risk by validating your setup before work begins.

Core Features & Use Cases

  • Install Integrity Verification: Checks for required tooling (bash ≥4, jq, git, etc.), valid harness manifests, present pipeline skills, and absence of projection drift between your checkout and the roster source.
  • Dev Environment Pre-Flight: Detects your project's build, test, and lint/format commands, verifies required tools are installed, and confirms commands execute successfully before work starts.
  • Clear Remediation Guidance: Reports exact missing components or misconfigurations, and offers to install missing tools or fix issues only with your explicit approval.
  • Use Case: Run this skill when you ask "is my setup ok", before starting a roster implementation phase, or when pipeline runs fail unexpectedly due to environment issues.

Quick Start

Invoke the roster-doctor skill to run a full health check of your roster installation and project development environment to confirm all components are functional before starting pipeline work.

Frequently Asked Questions about roster-doctor

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

FAQPage Schema
How do I verify my roster installation and dev environment before starting pipeline work?

Run a preflight health check to verify your roster installation integrity and dev environment runnability. This validates required tooling presence, harness manifest correctness, and pipeline skill availability to prevent pipeline failures from broken setups.

What does a dev environment preflight check inspect in a roster-managed project?

A dev environment preflight check detects your project's build, test, and lint commands, verifies required tools like bash, jq, and git are installed, and confirms gate commands execute successfully. It also validates harness manifests and checks for projection drift.

Why do my roster pipeline runs fail unexpectedly due to environment issues?

Pipeline runs fail when required tooling is missing, harness manifests are invalid, pipeline skills are absent, or projection drift exists between your checkout and roster source. Running install verification diagnostics identifies these exact misconfigurations before work begins.

Do I need specific tools installed to pass a roster install verification?

Yes, install verification requires specific tooling including bash version 4 or higher, jq, and git. The health check validates these required tools are present and offers to install missing components only with your explicit approval.

Can I fix missing components automatically when a dev environment health check fails?

The health check offers to install missing tools or fix issues only with your explicit approval. It reports exact missing components and misconfigurations, providing clear remediation guidance without automatically modifying your source code.

When should I run an install verification check for my roster development environment?

Run install verification when asking if your setup is ok, before starting a roster implementation phase, or when pipeline runs fail unexpectedly. It serves as a pre-pipeline preflight check and provides on-demand health diagnostics for roster-managed tasks.