From tend-ci-runner
Debug and fix failing CI on the default branch. Use when CI fails on main.
npx claudepluginhub max-sixty/tend --plugin tend-ci-runnerThis skill uses the workspace's default tool permissions.
CI has failed on the default branch. Diagnose the root cause, fix it, and create a PR.
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.
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.
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.
Share bugs, ideas, or general feedback.
CI has failed on the default branch. Diagnose the root cause, fix it, and create a PR.
Failed run: $ARGUMENTS
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).
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.
gh run view <run-id> --log-failedRe-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)
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.