Menu
Autonomously diagnose and fix a failing CI pipeline on the current branch.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Mandatory rules for general git use in this repository. Follow these constraints before starting work, committing, or pushing.
Use for any Go code writing, refactoring, or review in starbunk-go. This agent cares about clean, idiomatic, readable Go — thoughtful naming, aesthetic structure, and code that feels good to read.
Comprehensive health check that runs build, test, lint, builds docker containers, checks container health/status, and reports to the user.
Feature developer and task runner agent. Start a new task on a fresh branch, orchestrate worktrees, do the implementation work, and open a PR when done.
PR Comment Addresser agent. Fetches all unresolved PR comments, evaluates their relevance, lists them for the user to select from, implements the selected fixes, and closes the addressed (and skipped) comments while ignoring new ones.
High-level architecture and planning for starbunk-go. Use when planning significant changes, reviewing cross-cutting concerns, coordinating multi-agent work, or evaluating the impact of a proposed change before implementation begins.
| name | ci-diagnose |
| description | Autonomously diagnose and fix a failing CI pipeline on the current branch. |
Follow these steps to autonomously diagnose and resolve CI failures on the current branch.
Find Latest Failed Run: Run the following command to retrieve the list of recent runs for the current branch and locate the latest failure:
gh run list --branch $(git branch --show-current)
Retrieve Failure Logs: Query the detailed failure logs for the specific failed Run ID identified:
gh run view [RUN_ID] --log-failed
Reproduce Locally:
Run the exact linter command, test command, or build step reported in the failure log on your local environment (e.g. running specific linters, go test ./..., or container builds).
Fix the Root Cause: Resolve the root issue, checking for configuration schema mismatches, version alignment, or code bugs. Do not just address the symptom.
Local CI Check: Before committing, run the full suite of local validations:
golangci-lint run ./...
go test ./...
Ensure any pre-commit hooks also pass cleanly.
Commit & Push: Commit your changes using a conventional commit message:
git commit -m "fix(ci): [description of root cause]"
git push origin $(git branch --show-current)
Verify Pipeline Execution: Wait 30 seconds, then check the run list again to verify that the CI pipeline is running and progressing:
gh run list
Iterate: If CI fails again with a DIFFERENT error, repeat starting from step 2. If it fails with the SAME error, your local reproduction was incorrect; investigate the environment or reproduction command deeper. Do up to 3 iterations. Report what you fixed and why it broke.