ci-fix

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

1. Get failure logs: gh run view <run-id> --log-failed
2. Identify the failing job and root cause — don't just fix the symptom
3. Search for the same pattern elsewhere in the codebase
4. Reproduce locally using test commands from the project's CLAUDE.md
5. 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 <[email protected]>"
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.