القائمة
Diagnose and fix failing CI on a PR. Capped at 3 attempts. Load repo-setup first.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Refresh /workspace/repo and prepare the correct branch. Load this before any situation skill.
Resolve a GitHub issue end-to-end — explore, plan, implement, clean up, and open a draft PR.
Review a pull request. Self-fix on own PRs, post a review on others'. Load repo-setup first.
Review the current branch's changes against intent. Returns a structured list of findings the caller can hand to a fix-applier, or an empty list when there's nothing to address. Use this for both self-review of your own work and reviewing someone else's PR.
Apply review findings as the smallest code changes, then commit and push. Used on the bot's own PRs.
Triage and respond to comments on a PR. Fix if actionable, reply either way. 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 existing attempts:
ATTEMPTS=$(gh api "repos/<owner>/<repo>/issues/<number>/comments" --paginate \
--jq '[.[] | select(.user.login == "'"$ME"'" and (.body | startswith("fix-ci: attempt")))] | length')
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.