Menu
Check release readiness across all components. Verifies CI status, security gates, and feature flag states for a go/no-go decision.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Generate a CI health report for a component or the entire organization. Uses controller analytics, run history, and security posture.
Create a Jira ticket from a build failure, security finding, or improvement recommendation.
Manage feature flags — list, inspect, enable, disable, or create flags. Supports progressive rollout workflows.
Show a unified view of all CI/CD pipelines across Jenkins, GitHub Actions, and CloudBees Workflows. The cross-tool picture no single tool can provide.
Analyze security posture across components. Shows vulnerabilities by severity, scanner type, SLA status, and remediation priority.
Analyze the latest failed CI run for a component. Identifies failing jobs and steps, reads logs, determines root cause, and classifies the failure.
| name | release-status |
| description | Check release readiness across all components. Verifies CI status, security gates, and feature flag states for a go/no-go decision. |
| argument-hint | [application-name or empty for all] |
components_list — get all components in the organization
For each component:
a. workflow_list — identify CI and release workflows
b. runs_list(limit=5) — get latest run status per workflow
Skip code_scan workflows.
c. security_issues_open_get or security_findings_summary_get —
check for open vulnerabilities on the default branch
d. branches_list — verify the default branch
Check release orchestration:
a. Look for components with release/deploy workflows
(workflow_dispatch triggers, staged deployments)
b. automation_jobs_list — check for staged deployment jobs
(staging -> approval -> production pattern)
c. Check for PENDING_APPROVAL jobs — these are deployment gates
waiting on human sign-off
Check feature flags:
a. flags_applications_list — find flag applications
b. flags_environments_list — list environments (staging, production)
c. flags_configurations_list — check flag states per environment
Present a release readiness report:
Release Readiness Report Date: [timestamp] Verdict: READY / NOT READY / BLOCKED
| Component | CI Status | Security | Flags | Blocker |
|---|---|---|---|---|
| name | GREEN/RED | N HIGH | state | desc |
Blockers by Priority:
What Must Be Done Before Release:
Offer next actions:
workflow_trigger (with explicit
user confirmation — show which workflow will be triggered and
what it will do before executing)