code-quality-audit

Audit codebases for structural quality violations via lint, type, format checks.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill code-quality-audit-grimlor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-audit
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/code-quality-audit
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill code-quality-audit-grimlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality audits often miss the real reasons problems exist, fail to distinguish out-of-scope issues, and silently ignore suppressions or BDD boundary mistakes—leaving future failures harder to diagnose.

Core Features & Use Cases

  • Systematic structural inspection: Runs lint, type-check, and formatting drift checks to surface mechanical issues first.
  • Mock boundary enforcement: Identifies when mocks patch internal/private details rather than true I/O boundaries.
  • Test-only production API detection: Finds production symbols that appear to be used only by tests and recommends safer alternatives.
  • Suppression pragma classification: Scans and categorizes suppression patterns into removable, external, or justified.
  • BDD convention compliance audit: Verifies BDD-style docstrings, GIVEN/WHEN/THEN structure, test organization, and assertion quality.

Quick Start

Ask an agent to use code-quality-audit to audit the files your spec targets and generate a findings document with actionable alternatives for every issue it detects.

Frequently Asked Questions about code-quality-audit

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

FAQPage Schema
How do I perform a code quality audit that finds mock boundary and test-only API pollution?

BDD convention audits verify that test docstrings follow GIVEN/WHEN/THEN structures and check test organization quality to surface convention violations before they spread, producing categorized findings with recommended alternatives.

What is the best way to audit suppression pragmas and formatting drift in a codebase?

Auditing suppression pragmas and formatting drift involves running mechanical lint and type checks first, then scanning and categorizing suppression patterns into removable, external, or justified classifications without expanding the audit scope.

How do I identify mocks patching internal details instead of true I/O boundaries?

Code quality audits can be run during feature workflow Phase 4, refactor workflow Phase 3, during remediation passes, or as a standalone review using an explicitly scoped file set to ensure structural violations are caught systematically.

Does a structural code review check BDD testing conventions and assertion quality?

A structural code review verifies BDD-style docstrings, GIVEN/WHEN/THEN structure, test organization, and assertion quality, applying systematic checks to catch convention violations and document charitable intent for detected issues.