# Fix Pipeline

> Check GitHub pipeline status and plan fixes if failing

- Skill: `alexanderop/fix-pipeline` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alexanderop/fix-pipeline`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexanderop/fix-pipeline/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: alexanderop (https://skillmd.com/u/alexanderop)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexanderop/fix-pipeline

---


# 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

1. **Check the run status** from the `<check_runs>` section above.
2. If all checks are passing, inform the user and stop.
3. If any checks are failing, proceed to Step 2.

### Step 2: Gather Failure Details

1. **Examine the failed logs** in `<latest_run_details>`.
2. If more details are needed, use `gh run view <run-id> --log-failed` to get specific failure information.
3. 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:

1. **Summarize the failures** clearly for the user.
2. **Enter plan mode** using the EnterPlanMode tool.
3. 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