aposd-audit

aposd audit — Design Quality Audit

Run systematic design quality checks and generate a comprehensive report. Don't fix issues; document them for review.

This is a code-level design audit — check what's measurable and verifiable in the implementation. Every dimension is scored by counting concrete, observable constructs. Fix the count → score goes up, every time.

Follows the impeccable audit convention: measure what's objectively countable, not what's interpretive.

Scoring rubric: Score each dimension 0-4. Total /20. Rating bands: 18-20 Excellent, 14-17 Good, 10-13 Acceptable, 6-9 Poor, 0-5 Critical.

Quick Start

aposd audit src/          # audit a directory
aposd audit src/services/order-service.js  # audit a single file
aposd audit               # defaults to workspace root

The report is printed to stdout.

Scope

This skill audits a single codebase target per invocation. It measures 5 design dimensions by counting observable constructs — pass-throughs, duplication, documentation gaps, naming issues, and exception patterns. It does not evaluate functional correctness, runtime performance, or test coverage. Each dimension is scored 0-4 from concrete evidence only.

What this skill does NOT cover:

• Functional correctness — does the code produce the right output?
• Runtime performance — how fast does it execute?
• Test coverage — are there enough tests?
• Security vulnerabilities — are there injection flaws or auth gaps?
• Code style / formatting — does it follow lint rules?
• Architectural fitness — are you using the right pattern for the job?
• Business logic completeness — are all requirements implemented?

Setup

Resolve the target to a concrete file path, directory, or module name. If no target is specified, default to the current workspace root directory.

Full scan: Scan all files in the target — no sampling. For large targets (>50 files), use sub-agents to parallelize the scan across directory groups.

Input / Output