القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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.
Check release readiness across all components. Verifies CI status, security gates, and feature flag states for a go/no-go decision.
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 | pipeline-overview |
| description | 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. |
| argument-hint | [component-name or 'all'] |
Show the user a unified view of their CI/CD pipelines across all tools.
If the user specified a component name, search for it using
components_search. Otherwise, list all components with components_list.
For each component, gather:
a. workflow_list — all configured workflows (CloudBees + GitHub Actions)
b. runs_list(limit=3) — the 3 most recent runs per workflow
c. Skip any workflows with names containing "code_scan" — these are
infrastructure-managed scans, not user pipelines
Get controller data:
a. controllers_list — find Jenkins controllers
b. For each controller: controllers_data_get(ci4) — runs overview
(active runs, queued, wait times)
Get security context:
a. security_issues_all_get — open vulnerability count per component
Get feature flag context:
a. flags_applications_list — find flag applications
b. For each application: flags_list — count of active flags
Present a unified dashboard:
Organization Pipeline Status
| Component | GitHub Actions | CloudBees Workflow | Jenkins | Security | Flags |
|---|---|---|---|---|---|
| name | #N PASS/FAIL | #N PASS/FAIL | status | N HIGH | N active |
For each component, show:
Provide a summary:
Offer next actions:
