Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Analyze GitHub Actions failures and propose fixes. Use when a user shares a failing GitHub Actions run URL/id, says 'CI is failing', asks 'why did this workf...
Analyze GitHub Actions failures and propose fixes. Use when a user shares a failing GitHub Actions run URL/id, says 'CI is failing', asks 'why did this workf...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Fetch GitHub Actions run details, pinpoint the failure, and propose a minimal fix. This skill is meant to feel like a senior engineer doing a fast βCI autopsyβ.
Collect evidence, explain root cause, propose fixes. No pushes, no PRs, no branch creation.
PR fix mode is allowed only when both are true: The user explicitly asks to open a PR. A local toggle is enabled (the βon/off buttonβ): env var: CI_WHISPERER_WRITE=1 If the toggle is not enabled, refuse politely and explain how to enable it.
Accept any of: workflow run URL run id PR number (then locate latest run) Always determine: owner/repo run id If the user didnβt specify the repo, ask for it (or infer from context).
Prefer deterministic tooling. Use /usr/bin/gh when the system has multiple gh binaries. Suggested commands: gh run view <run-id> --repo owner/repo --json status,conclusion,createdAt,updatedAt,event,headBranch,headSha,url,name gh run view <run-id> --repo owner/repo --log-failed gh run view <run-id> --repo owner/repo --log (only if needed; can be noisy) If gh is not authenticated, stop and ask the user to run: /usr/bin/gh auth login
Return: failing job(s) and step(s) the exact error excerpt (short; redact secrets) likely root cause(s) ranked minimal fix options confidence level
If the user asks to fix it and CI_WHISPERER_WRITE=1: create a branch apply minimal changes run local lint/tests if available open PR with a clear description and link to the failing run If the user asks but write mode is OFF: provide the patch/diff instructions, but do not push.
Never print tokens. Donβt open PRs or push changes unless explicitly requested. If logs contain secrets, redact before quoting.
Use scripts for repeatable fetching and parsing: scripts/ci_autopsy.py (fetch run metadata + failed logs)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.