release-readiness-check

Aggregate GitHub, ArgoCD, and Jira data into a Go/No-Go release verdict.

392|73|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill release-readiness-check-cnoe-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-readiness-check
Source: https://github.com/cnoe-io/ai-platform-engineering/tree/main/ui/src/skills/release-readiness-check
Command: npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill release-readiness-check-cnoe-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.

Core Features & Use Cases

  • Orchestrates Phase 1 Code Readiness checks across GitHub PRs, CI/CD status, and recent commits
  • Verifies Phase 2 Environment Health across ArgoCD staging and production environments
  • Phase 3: Issue Resolution with Jira blockers, fixVersions, and QA sign-off tracking
  • Phase 4 Release Verdict producing a Go/No-Go decision and a structured readiness report
  • Output: Consistent generation of a release readiness report for stakeholders

Quick Start

Invoke the Release Readiness Check against your target release branch to generate a comprehensive pre-release report.

Frequently Asked Questions about release-readiness-check

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

FAQPage Schema
How do I verify release readiness before deploying to production?▼

You can verify release readiness by aggregating GitHub PRs, CI/CD status, ArgoCD environment health, and Jira issue blockers into a single Go/No-Go decision report.

What does a Go/No-Go release readiness check include?▼

A Go/No-Go readiness check evaluates code readiness via GitHub PRs and CI/CD, verifies ArgoCD staging and production health, and tracks Jira blockers to produce a final verdict.

Can I check ArgoCD staging and production health during release planning?▼

Yes, release readiness checks verify ArgoCD staging and production environment health as part of the workflow to ensure all prerequisites are met before cutting a release.

How do I track Jira blockers and QA sign-off for a release decision?▼

You can track Jira blockers, fixVersions, and QA sign-off by aggregating issue data across staging and production workflows to inform the final Go/No-Go release decision.

Does release readiness validation work with GitHub PRs and CI/CD pipelines?▼

Yes, release readiness validation orchestrates checks across GitHub PRs, recent commits, and CI/CD pipeline status to confirm code readiness before generating the final report.