| name | fix-pipeline |
| description | Check GitHub pipeline status and plan fixes if failing |
| allowed-tools | Bash(gh pr checks:*), Bash(gh run list:*), Bash(gh run view:*), Bash(gh api:*), Bash(git rev-parse:*), Bash(git branch:*), EnterPlanMode |
Check Pipeline Status
I have gathered information about your pipeline. Here are the results:
<current_branch>
!git rev-parse --abbrev-ref HEAD
</current_branch>
<check_runs>
!gh run list --branch $(git rev-parse --abbrev-ref HEAD) --limit 5
</check_runs>
<latest_run_details>
!gh run view --branch $(git rev-parse --abbrev-ref HEAD) --log-failed 2>/dev/null || echo "No failed logs available"
</latest_run_details>
Instructions
Step 1: Analyze Pipeline Status
- Check the run status from the
<check_runs> section above.
- If all checks are passing, inform the user and stop.
- If any checks are failing, proceed to Step 2.
Step 2: Gather Failure Details
- Examine the failed logs in
<latest_run_details>.
- If more details are needed, use
gh run view <run-id> --log-failed to get specific failure information.
- Identify the root cause of the failure (test failures, lint errors, type errors, build issues, etc.).
Step 3: Enter Plan Mode
If the pipeline is failing:
- Summarize the failures clearly for the user.
- Enter plan mode using the EnterPlanMode tool.
- In plan mode, create a detailed plan to fix the issues, including:
- What specifically failed
- Which files need to be modified
- The steps to fix each issue
- How to verify the fix locally before pushing