roster-audit

Audit codebases for quality issues and spec compliance with cited findings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing code for quality issues and spec compliance is time-consuming, inconsistent, and often misses critical violations that lead to regressions or misaligned implementations. This skill eliminates that friction by producing a single, prioritized report of cited, actionable findings.

Core Features & Use Cases

  • Combined Quality & Compliance Checks: Evaluates function size, DRY violations, naming consistency, spec adherence, invariant preservation, and architectural conformance in one pass.
  • Knowledge Base Integration: Validates code against your project's spec, properties, glossary, and architecture docs when available, or uses configurable default thresholds if no knowledge base exists.
  • Flexible Scoping: Audit an entire codebase, a specific directory, or a git commit range to focus on exactly the code you care about.
  • Use Case: Before shipping a new feature, run this audit to catch hidden quality issues and spec deviations before they reach production, or use it to assess the overall health of a legacy codebase.

Quick Start

Use the roster-audit skill to run a full quality and compliance audit of your current codebase and receive a prioritized list of file-and-line cited findings to address.

Frequently Asked Questions about roster-audit

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

FAQPage Schema
How do I automate code quality and spec compliance audits for an existing codebase?

You can automate codebase audits by running a combined quality and spec compliance check that outputs a single prioritized report of cited, actionable findings addressing DRY violations, naming consistency, and architectural conformance.

What is a pre-ship code health assessment and when do I need one?

A pre-ship code health assessment is a combined quality and compliance validation run before deployment to catch hidden quality issues and spec deviations. You need one before shipping new features or when assessing legacy codebase health.

Can I scope a code audit to specific directories or git commit ranges?

Yes, code audits support flexible scoping to specific directories or git commit ranges, allowing you to focus the quality and spec compliance validation on exactly the code changes or areas you care about.

How do I validate code against project architecture and spec documentation?

Spec compliance validation checks code against your project's spec, properties, glossary, and architecture docs when available, enforcing invariant preservation and architectural conformance using configurable default thresholds if no knowledge base exists.

Does the audit enforce function size thresholds and DRY principles?

Yes, the audit enforces function size thresholds, DRY principles, naming consistency, spec adherence, invariant preservation, and architectural conformance in a single combined pass across the scoped codebase.

What's the best way to review legacy codebase health without manual inspection?

Running an ad-hoc codebase review audit is the best way to assess legacy health without manual inspection, generating a consolidated, prioritized report of file-and-line cited findings for quality and compliance issues.