fix-issues
Use when the user says 'fix issues' or asks why the current PR is not merge ready: merge conflicts, failing CI (Buildkite or GitHub Actions), failing build, or PR metadata problems. Does not handle re
SKILL.mdplugins/tony/skills/fix-issues/SKILL.md
GitHubFix Issues
Purpose
Find and fix everything other than review comments that blocks the current PR from being merge ready.
Invoking this skill is the explicit request to commit and push for this run. It does not carry over to any other work in the session.
Scope
- In: merge conflicts, failing Buildkite builds (if the repo uses
Buildkite), failing GitHub checks and build errors, PR metadata (title,
labels, description, draft state), and any other non-comment blocker
ghreports. - Out: review comments and review threads. Hand those to
tony:pr-comments.
Process
Find the PR. Run
gh pr view --json number,url,title,body,labels,isDraft,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,baseRefName. If it fails, stop and say what is missing.List every blocker before fixing any. Check:
mergeableandmergeStateStatus: conflicts or a stale base.statusCheckRollup: each failed or errored check, with its URL.- Buildkite, if
.buildkite/exists or a check links to buildkite.com: use the Buildkite MCP tools (get_build_failure_summaryfirst) to find failing jobs. - PR metadata: title format, labels, description, ticket link, draft state. Follow the repo's CONTRIBUTING and the user's global rules.
- Anything else
gh pr checksorgh pr viewflags. Ignore pending checks and soft failures. Skip review comments.
Classify each blocker as fixable here (code, merge, config, metadata) or not (needs approval, outside access, flaky infra). Report the second kind without acting on it.
Fix in this order:
- Merge conflicts: follow
tony:fix-merge-conflicts. - Build, lint, type, and test failures: reproduce locally, find the root cause from the logs, fix it. Do not retry a red build hoping it passes. Re-run only when the logs show a flake, and say so.
- PR metadata: fix with
gh pr edit.
- Merge conflicts: follow
Verify locally, then commit and push code fixes to the PR branch. Never force-push unless the user says so.
Re-check. Wait for checks to re-run and read the new status. If a blocker persists after two fix attempts, stop and ask.
Output
- Blockers found: each one and its source.
- Fixed: what changed, with the commit hash.
- Not fixed: each remaining blocker and why.
- Status: current merge readiness. Say if review comments remain
and suggest
tony:pr-comments.