code-quality-auditor

Audit source code against team-defined invariants and naming conventions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of checking code against your team's defined invariants, naming conventions, and quality thresholds, ensuring consistent, standards-compliant code across your entire codebase.

Core Features & Use Cases

  • Multi-Aspect Static Code Checks: Scans source code for function size violations, DRY (duplicate code) issues, naming inconsistencies against your team's glossary, invariant preservation gaps, and error handling flaws.
  • Structured Severity-Ranked Reporting: Generates a clear, actionable report that categorizes issues as Critical, Warning, or Info, with exact file locations, KB references, and specific fix recommendations.
  • Use Case: Imagine your team has a rule that no function can exceed 50 lines and all public API names must use canonical terms from your team's glossary. Use this Skill to automatically scan your codebase, flag every violation with precise context, and get a prioritized list of fixes to enforce your standards.

Quick Start

Use the code-quality-auditor skill to scan your project's source code and generate a full code quality report against your team's knowledge base rules.

Frequently Asked Questions about code-quality-auditor

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

FAQPage Schema
How do I audit source code against team naming conventions and invariants?

You can audit source code by scanning it against a populated knowledge base directory containing team properties, glossary, and specification files to enforce consistent code quality standards automatically.

What is static code analysis for DRY violation detection and function size checks?

Static code analysis is the process of scanning source code without executing it to detect DRY violations, function size threshold breaches, and naming inconsistencies against team-defined rules.

Do I need a knowledge base directory to check code quality standards?

Yes, a populated knowledge base directory with properties, glossary, and specification files is required to validate naming consistency and verify invariant preservation during the code audit.

Can I enforce error handling patterns and naming glossaries automatically?

Yes, you can enforce error handling patterns and validate public API names against canonical team glossaries by running static code checks that flag inconsistencies with precise file locations.

What's the best way to generate a severity-ranked code quality report?

The best way to generate a severity-ranked report is to scan your codebase against team knowledge base rules, categorizing issues as Critical, Warning, or Info with exact file locations and fix recommendations.

Does the code audit rely on external dependencies or built-in shell tools?

The code audit relies exclusively on built-in shell tools for static analysis, requiring no external dependencies to perform function size checks, DRY violation detection, and invariant verification.