verify

Automated quality checks prevent premature completion claims by enforcing evidence-driven validation through lint, typecheck, and test commands. This skill runs a phase-driven audit against your target and produces fresh verification logs under the logs/ directory to prove work is actually done.

The best way to purge legacy dead-code and refresh documentation is running a phase-driven assessment that includes governance gates and cross-package impact checks. This skill targets files or packages, identifies backward-compat dead-code for removal, and updates affected docs automatically.

Yes, you can run cross-package impact checks and surface QA on specific files, packages, or blueprint slugs. By executing /verify <target>, the skill initiates a phase-driven audit that validates the specified target and reports success or remediation needs.

Evidence-based validation works without external dependencies, relying on built-in lint, typecheck, and test commands to generate verification logs. The skill operates independently to enforce governance gates and surface QA, producing an evidence log under logs/ that confirms completion status.

Your verification audit reports remediation needs when lint, typecheck, or test commands fail during the phase-driven assessment. The skill enforces evidence-driven checks that guard against premature completion, requiring fresh verification logs to prove all governance gates and surface QA validations passed.

To validate implementation completion, run /verify <target> against your files, packages, or blueprint slugs. The skill executes lint, typecheck, and test commands, performs governance and cross-package impact checks, purges legacy code, refreshes docs, and outputs an evidence log under logs/.