// Diagnose and fix failing CI on a PR. Capped at 3 attempts. Load repo-setup first.
Auto-merge a PR after it is marked ready-for-review, if the change is small, non-disruptive, and all checks pass.
Promote a draft PR to ready-for-review after CI passes and self-review is clean. Assigns reviewers and adds labels.
Clone or refresh a GitHub repo and prepare the working tree. Load this before any situation skill.
Resolve a GitHub issue end-to-end — explore, plan, implement, clean up, and open a draft PR.
Triage and respond to comments on a PR. Fix if actionable, reply either way. Load repo-setup first.
Review a pull request. Self-fix on own PRs, post a review on others'. Load repo-setup first.
| name | fix-ci |
| description | Diagnose and fix failing CI on a PR. Capped at 3 attempts. Load repo-setup first. |
| license | Apache-2.0 |
| metadata | {"audience":"autonomous-agents"} |
Fix failing CI on a PR the bot authored. Load repo-setup first.
3 attempts max per PR. Count comments that start with
fix-ci: attempt on the PR. If >= 3, BLOCKED. Otherwise post a
short comment like "fix-ci: attempt 2 — looks like a type error in
foo.ts, investigating" before starting work. The fix-ci:
prefix is required for counting but the rest should read naturally.
gh run list --branch <branch> --status failuregh run view <id> --log-failedreferences/failure-taxonomy.md for
the full taxonomy and decision tree. Categories: test failure,
type/lint error, build error, snapshot diff, flaky test, or infra
issue.gh run rerun <id> --failed) and stop.deslop and review skills.Avoid modifying CI config unless the failure is specifically in it. Avoid bumping dependency versions — the fix should target the code, not the toolchain. Don't force-push. Don't merge.