assess-release-readiness

To check release readiness, you can analyze a code branch for incomplete work like TODOs, security concerns, runtime errors, and missing files. This process evaluates changes against release criteria to surface blockers and generate a readiness verdict before merging to main.

Branch readiness analysis inspects code changes to determine if a branch is releasable. It returns a JSON object containing a releasable flag, a verdict, identified concerns, and actionable pre_release and post_release instructions to guide the deployment process.

You can extract actionable pre-release items by analyzing the branch for documentation updates, version bumps, or missing files to stage. This evaluation surfaces a concise todo list of concerns and instructions required to satisfy release criteria.

Yes, release readiness analysis is applicable to QA processes and change-risk assessments. By inspecting branch changes for security concerns and runtime errors, it evaluates the risk profile and determines whether the code is safe for release.

To assess release risks, you should look for incomplete work marked by TODO, FIXME, or XXX comments, along with security concerns, runtime errors, and missing files. Identifying these issues ensures the branch meets the required release criteria.