القائمة
CI debugging workflow guide for self-hosted runners. Use when learning CI debugging workflows, understanding failure patterns (F01-F12), or troubleshooting GitHub Actions on self-hosted runners.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Find root causes systematically before fixing — trace the causal chain and form hypotheses with predictions for uncertain links. Use when debugging errors, test failures, stack traces, or when stuck after failed fix attempts. For delegating a stuck investigation to an independent Codex session, use /codex:rescue.
Standard pattern for querying ruvector institutional memory before acting. Use when authoring new agents or commands that should query past patterns, findings, or solutions before executing.
Shared conventions for CI analysis — validation rules, failure patterns, error catalog, and security patterns. Use when agents or commands need CI-specific validation or pattern matching reference.
Canonical conventions for shelling out to the OpenAI Codex CLI. Use when authoring or modifying commands or agents that invoke codex exec — choosing flags, sandbox and approval modes, and parsing its output.
Canonical conventions for running batch workflows through the Composio MCP server. Use when authoring or modifying commands or agents that call Composio tools — the Workbench sandbox, Multi-Execute batching, and the local usage counter.
Expert guidance for creating Claude Code skills and agents. Use when working with SKILL.md files, authoring new skills, creating slash commands, or designing agent workflows.
| name | diagnose-ci |
| description | CI debugging workflow guide for self-hosted runners. Use when learning CI debugging workflows, understanding failure patterns (F01-F12), or troubleshooting GitHub Actions on self-hosted runners. |
| user-invokable | true |
Explains how to understand and resolve GitHub Actions workflow failures on self-hosted runners, including the F01-F12 failure-pattern catalog.
Use when learning CI debugging workflows, understanding failure patterns, or need guidance on troubleshooting self-hosted runner issues. This skill provides contextual knowledge that agents and commands reference during CI analysis.
/ci:status/ci:diagnose [run-id]/ci:runner-health [runner-name]Symptoms: Exit code 137, Killed, No space left on device
Workflow:
/ci:diagnose to confirm pattern/ci:runner-health to check current resource state/ci:runner-cleanup to free spaceSymptoms: command not found, tests pass locally but fail in CI
Workflow:
/ci:diagnose to identify missing tool or stale stateclean: true to checkout step/ci:lint-workflows to catch other self-hosted pitfallsSymptoms: Cannot connect to Docker daemon, rate limiting
Workflow:
/ci:diagnose to confirm Docker pattern/ci:runner-health — verify Docker status/ci:runner-cleanupSymptoms: Intermittent failures, passes on re-run
Workflow:
/ci:diagnose on last 3-5 failures to identify patternSymptoms: Runner offline, heartbeat timeout, Runner.Listener crash
Workflow:
/ci:runner-health runner-name12 categories cover self-hosted runner issues (F01-F12). The ci-conventions
skill contains the full pattern library with log signals, severity levels, and
detailed fix suggestions.
Run /ci:lint-workflows before pushing workflow changes to catch common
self-hosted pitfalls (14 rules, W01-W14).