Diagnose failing PR checks and apply minimal fixes until CI passes.
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill fix-ci-zanzythebar
Please help me install this Agent Skill. Skill: fix-ci Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/fix-ci Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill fix-ci-zanzythebar
gh pr checks as the source of truth to identify failing jobs, workflows, and external check links. - Iterative Focused Fixes: Extracts the first actionable error from GitHub Actions logs and applies the smallest safe fix, one failure at a time. - Guarded Push Behavior: Only pushes and re-checks CI when the user explicitly requested CI repair or approved pushing, and never bypasses hooks or force-pushes. - Use Case: A pull request shows three failing checks. The Skill inspects the logs, finds a lint error, fixes it, re-runs local validation, and reports the current CI status with the next action. ## Quick Start Ask the assistant to investigate why the current pull request checks are failing and fix them one at a time until CI is green.High-intent search queries and answers about installing and using this skill.
Run gh pr checks with JSON output to list each check's name, state, workflow, and link. Then inspect the failed job's GitHub Actions logs to extract the first actionable error before attempting any fix.
Fix one actionable failure at a time with the smallest safe change, re-run the relevant local validation, then push only with approval. Repeat the inspect-fix-validate loop until all checks pass or progress is blocked.
Yes, the workflow relies on the gh CLI, specifically gh pr checks, as the source of truth for overall PR CI state. External check links are used only when GitHub Actions logs are unavailable.
No, pushing happens only when the user explicitly asked for CI repair on a PR or approved pushing. The guardrails also prohibit bypassing hooks, force-pushing, or hiding unrelated changes.
It addresses one failure cause at a time and prefers minimal low-risk changes over broad refactors. Systemic failures, flaky infrastructure, or issues requiring architectural changes may leave the workflow blocked rather than green.
Chorus-AIDLCAutomate pull request workflows with git and the GitHub CLI.
leandro-br-devCoordinate production deployments with environment validation and post-deploy checks.
matteingRun the full CI suite locally to verify Elixir and TypeScript checks before pushing.
SocketDevRun GitHub Actions workflows locally in Docker and retry failed steps until green.