release-check

Release readiness checks evaluate pending repository changes against baseline criteria. The audit runs security scans, intent-skill gates, and unit tests to produce a summary of blockers and recommendations before committing.

Pre-commit readiness checks audit pending changes across source, docs, and config files. The mechanism runs security scans, dependency hygiene checks, and intent-skill coverage gates to validate code before committing.

Diff-based impact assessment classifies touched areas like src, docs, and config directories. This focuses review and validation efforts exactly where changes occurred to determine overall release readiness.

Yes, security scans and unit tests are baseline checks for release readiness. The workflow executes these alongside an intent-skills gate to certify whether pending changes are ready to merge.

A release readiness report includes pass/fail status, specific blockers with exact commands, and recommended next steps. It provides a clear summary of change readiness for stakeholders.

Automated release checks may not suffice for complex architectural changes. The baseline checks focus on security scans, unit tests, and intent-skill gates, which may miss context-specific logic flaws requiring manual review.