Release Audit

Overview

Aggregator and router for release readiness: detect what the repo actually ships, dispatch only the matching focused audit skills, and synthesize one scorecard with an ordered ship-blocker list. This is a readiness GATE, not a remediation plan — if the human wants the full audit-to-fix-spec pipeline afterward, route them to nuke-audit.

When to use / when NOT

Use when:

• A human asks whether a project is ready to ship/release/publish/deploy and wants one answer.
• Before a version tag, first npm/PyPI publish, docs launch, or making a repo public.
• The human cannot or does not want to enumerate the individual audit dimensions.

Do NOT use when:

• The question is single-dimension ("is the docs site deployable?") — invoke that focused skill directly (e.g. docs-deploy-readiness).
• The human wants the fixes planned and executed — that is nuke-audit.
• Mid-feature code review — use code-audit or a normal review flow.

How it works