-
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:
- [Highest priority blocker with specific details]
- [Next blocker]
...
What Must Be Done Before Release:
-
Offer next actions:
- "/triage [component]" for any red component
- "/security-scan [component]" for components with findings
- "/flag-rollout [flag] enable" to activate flags for release
- Post release readiness to Slack
- Trigger release workflow via
workflow_trigger (with explicit
user confirmation — show which workflow will be triggered and
what it will do before executing)