assess-release-readiness

Analyze a code branch for release readiness and return a JSON verdict.

1|Updated Jan 15, 2026

Search Tags:#automation #QA #code-quality #branch #analyze #release-readiness

Ready to run

npx skills add https://github.com/qmu/workaholic --skill assess-release-readiness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: assess-release-readiness
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/assess-release-readiness
Command: npx skills add https://github.com/qmu/workaholic --skill assess-release-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes a code branch to determine release readiness by inspecting changes for issues such as incomplete work (TODO, FIXME, XXX), security concerns, runtime errors, and missing files.

Core Features & Use Cases

Release readiness analysis: Evaluate changes against release criteria to surface blockers and actionable items.
Actionable items extraction: Identify documentation updates, version bumps, or files to stage before release.
Use Case: Before merging to main, run this Skill to generate a concise readiness verdict and a todo list for the release.

Quick Start

Use the assess-release-readiness skill to generate a release assessment for the current branch and receive a JSON summary including the releasable flag, verdict, concerns, and pre_release/post_release instructions.

Frequently Asked Questions about assess-release-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check release readiness for a code branch before merging?▼

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.

What is branch readiness analysis and what does it return?▼

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.

How do I extract actionable pre-release items from code changes?▼

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.

Can I use release readiness analysis for QA change-risk assessments?▼

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.

What specific issues should I look for to assess release risks?▼

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.