cnoe-io/release-readiness-check
charts/ai-platform-engineering/data/skills/release-readiness-check/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add cnoe-io/ai-platform-engineering release-readiness-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:51 PM4.2s2 files scanned
SKILL.md
- name:
- release-readiness-check
- description:
- 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.
Release Readiness Check
Orchestrate GitHub, ArgoCD, and Jira agents to perform a comprehensive pre-release verification covering code readiness, environment health, and issue resolution.
Instructions
Phase 1: Code Readiness (GitHub Agent)
- Check open PRs targeting release branch
- CI/CD status on the release branch
- Recent commits and conventional commit compliance
- Release artifacts - changelog, version bump, Docker images
Phase 2: Environment Health (ArgoCD Agent)
- Staging environment - synced, healthy, correct version
- Production environment baseline - healthy before deploying
- Helm chart versions updated
Phase 3: Issue Resolution (Jira Agent)
- Blocking issues - release-blockers, p0
- Testing status - QA sign-off, regression results
- Documentation - release notes, breaking changes, ADRs
Phase 4: Release Verdict
Compile all checks into a Go/No-Go decision with clear justification.
Output Format
```markdown
Release Readiness Report
Release: v2.4.0 Verdict: GO / NO-GO / CONDITIONAL
Readiness Checklist
| Category | Check | Status | Details | |----------|-------|--------|---------| | Code | All PRs merged | PASS | 0 open PRs | | Code | CI checks passing | PASS | All 12 checks green | | Env | Staging healthy | PASS | All 15 apps synced | | Issues | No release blockers | FAIL | 1 blocker open | ```
Examples
- "Are we ready for a release?"
- "Check release readiness for v2.4.0"
- "Is staging healthy and can we deploy to production?"
- "Are there any release blockers in Jira?"
Guidelines
- A single failing critical check makes the verdict NO-GO
- Warnings make the verdict CONDITIONAL (can proceed with acknowledgment)
- Always include a rollback plan in the readiness report
- Check for breaking changes and verify they have corresponding ADRs
- Never skip the staging health check
- Include DCO sign-off verification for all commits in the release
Related Skills
cnoe-io/streaming-testing
testing
VerifiedTrustedCommunity
Compare A2A streaming behaviour across supervisor versions. Captures SSE events, analyzes metadata flags (is_narration, is_final_answer), and produces side-by-side comparison reports.
345SKILL.mdUpdated Apr 15, 2026
cnoe-io/sprint-progress-report
testing
VerifiedTrustedCommunity
Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/security-vulnerability-report
development
VerifiedTrustedCommunity
Scan GitHub repositories for security vulnerabilities including Dependabot alerts, code scanning results, and secret scanning findings. Use when auditing repository security, preparing compliance reports, or triaging vulnerability alerts.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/review-specific-pr
development
VerifiedTrustedCommunity
Perform a comprehensive code review of a specific GitHub Pull Request. Analyzes code changes, checks for bugs, security issues, test coverage, and coding standards compliance. Use when a user provides a PR URL or asks to review a specific pull request.
345SKILL.mdUpdated Apr 4, 2026