Skill

ci-fix

Debug and fix failing CI on the default branch. Use when CI fails on main.

npx claudepluginhub max-sixty/tend --plugin tend-ci-runner

Tool Access

This skill uses the workspace's default tool permissions.

Preview

CI has failed on the default branch. Diagnose the root cause, fix it, and create a PR.

SKILL.md

Similar Skills

ci-fix

Detects GitHub Actions CI failures in PRs, analyzes logs with gh CLI, fixes code, commits and pushes changes, then re-verifies up to 3 retries until passing.

2 files

ci-fix

fix-ci

Diagnoses and fixes GitHub Actions CI failures in pull requests by fetching job logs, identifying root causes like build or test errors, and proposing targeted code changes.

core

gh-fix-ci

Inspects GitHub PR checks using gh CLI, fetches failing GitHub Actions logs, summarizes root causes, proposes fix plans, and implements code changes after user approval. Ideal for debugging PR CI/CD failures.

1 file

shipshitdev-library

Stats

Parent Repo Stars16

Parent Repo Forks0

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Fix CI on Default Branch

CI has failed on the default branch. Diagnose the root cause, fix it, and create a PR.

Failed run: $ARGUMENTS

Workflow

0. Load environment skills

Load /tend-ci-runner:running-in-ci first — it contains CI security rules, polling conventions, and comment formatting guidance. It will also prompt you to load any repo-specific skills (e.g., running-tend).

1. Check for existing fixes

gh pr list --state open --head "fix/ci-" --json number,title,headRefName

If an existing PR addresses the same failure, comment on it linking the new run and stop.

2. Diagnose and fix

Get failure logs: gh run view <run-id> --log-failed

Identify the failing job and root cause — don't just fix the symptom

Search for the same pattern elsewhere in the codebase

Reproduce locally using test commands from the project's CLAUDE.md

Fix at the right level (shared helper > per-file fix)

3. Create PR

Re-check for existing fix PRs (one may have been created while you worked).

git checkout -b fix/ci-<run-id> git add <files> git commit -m "fix: <description> Co-Authored-By: Claude <noreply@anthropic.com>" git push -u origin fix/ci-<run-id>

Create the PR with gh pr create. PR body format:

## Problem [What failed and the root cause] ## Solution [What was fixed and why this is the right level] ## Testing [How the fix was verified] --- Automated fix for [failed run](run-url)

4. Monitor CI

Poll CI using the approach from running-in-ci (loaded in step 0). If CI fails, diagnose with gh run view <run-id> --log-failed, fix, commit, push, and repeat.

Fix CI on Default Branch

CI has failed on the default branch. Diagnose the root cause, fix it, and create a PR.

Failed run: $ARGUMENTS

Workflow

0. Load environment skills

1. Check for existing fixes

gh pr list --state open --head "fix/ci-" --json number,title,headRefName

If an existing PR addresses the same failure, comment on it linking the new run and stop.

2. Diagnose and fix

Get failure logs: gh run view <run-id> --log-failed
Identify the failing job and root cause — don't just fix the symptom
Search for the same pattern elsewhere in the codebase
Reproduce locally using test commands from the project's CLAUDE.md
Fix at the right level (shared helper > per-file fix)

3. Create PR

Re-check for existing fix PRs (one may have been created while you worked).

git checkout -b fix/ci-<run-id>
git add <files>
git commit -m "fix: <description>

Co-Authored-By: Claude <noreply@anthropic.com>"
git push -u origin fix/ci-<run-id>

Create the PR with gh pr create. PR body format:

## Problem
[What failed and the root cause]

## Solution
[What was fixed and why this is the right level]

## Testing
[How the fix was verified]

---
Automated fix for [failed run](run-url)

4. Monitor CI

Poll CI using the approach from running-in-ci (loaded in step 0). If CI fails, diagnose with gh run view <run-id> --log-failed, fix, commit, push, and repeat.