Fix pull requests

Get every selected pull request to a passing state, then approve or merge it
only when asked. Otherwise report its exact blocker and next action. A pull
request is passing when it is not a draft, is up to date with its base, passes
every required check, and has no unresolved conflict. Process every pull
request independently; one blocked pull request must not stop the others. On
GitLab, "pull request" means merge request (MR); read
gitlab.md before inventory or diagnosis and substitute
its commands throughout. On any other platform, stop before any mutation and
name the unsupported platform.

Select the pull requests

The user may name pull requests in arguments or in plain words: numbers, URLs,
head branches, or a description such as "my PRs with auto-merge" or "the ones
I shipped today". Resolve a description against the inventory and state the
resolved list before the first mutation. Ask only when it matches nothing or is
ambiguous. Without a selection, take the user's open pull requests in the
current repository. Filters combine with AND.

The words "merge" or "approve" in the user's own text for those pull requests
count as the flags. Never infer either. The auto-merge selector does not
count as --merge.

Authorization

The invocation authorizes unattended work within
git-policy.md; do not pause between these actions:
read-only inspection, the smallest root-cause fix, the required local checks, a
normal push, a rebase with a lease-protected force-push on the user's own
branch, one eligible CI retry per run, a normal branch update on another
author's branch, and CI watching. When another skill such as ship loads this
one, skip the rebase and force-push: use a normal branch update, or report the
needed rebase. --approve, --merge, and enabled auto-merge add only what
merge.md allows.

• Read the repository's AGENTS.md, CLAUDE.md, CONTRIBUTING.md, and the CI
  documentation relevant to the failing check or changed paths. Apply the most
  specific rules.
• A branch is the user's own when the pull request author equals the login
  from gh api user and the head repository is the current repository. Only
  these branches may be rewritten. Never force-push without
  --force-with-lease=BRANCH:OBSERVED_SHA.
• Do not dismiss or request reviews, mark a draft ready, close a pull request,
  delete a remote branch, disable auto-merge (except the push pause in
  auto-merge-pause.md), change branch protection, bypass
  required checks, or push to a fork-owned branch. Report those blockers with
  the exact owner and next action.
• Never edit tests, lint, or CI configuration only to make a check pass; fix
  the cause or report the check as blocked.

Inventory

Run a fresh inventory at the start of every turn; do not rely on a list from a
previous turn.

git remote get-url origin
gh repo view --json nameWithOwner,defaultBranchRef,url
gh api user --jq .login
gh pr list --state open --limit 100 --author @me --json number,title,url,headRefName,headRefOid,baseRefName,author,isDraft,isCrossRepository,autoMergeRequest,mergeStateStatus,mergeable,reviewDecision

Replace --author @me with the parsed selection. If the list reaches its
limit, raise the limit until the inventory is complete. If the selection is
empty, report that and stop.

For each pull request record the fields above plus its required-check state.
Refresh this record after every mutation: a new head SHA makes earlier check
results stale.

Diagnose and repair

Use these read-only commands for each number N:

gh pr view N --json number,title,url,headRefName,headRefOid,baseRefName,author,isCrossRepository,headRepositoryOwner,isDraft,autoMergeRequest,mergeStateStatus,mergeable,reviewDecision,reviewRequests,reviews
gh pr view N --comments
gh pr checks N --required --json name,state,description,link,workflow,event

Classify the first real blocker, then check whether another needs attention.
Handle branch state before check state: a rebase restarts CI, so a fix pushed
to a stale branch wastes a run.

• mergeStateStatus is BEHIND, mergeable is CONFLICTING, or the
  repository requires linear history and the branch has merge commits: read
  branch-repair.md. Finish stacked base pull
  requests first.
• Required checks are pending, or the pull request is in a merge queue: read
  watch.md. Do not change code or rerun a running check.
• A check failed: open the linked run and read the failure, not only its
  summary: gh run view RUN_ID --log-failed, fetched by a cheap agent that
  returns the first error and up to 20 log lines. Treat a reproducible code
  failure as a fix and a proven service or runner failure as an eligible
  one-time rerun. Read check-repair.md. A second
  failure is a real failure.
• Review required, draft, permission, policy, or unknown state: report the exact
  message and owner (Authorization). A review blocker does not stop branch
  and check work.

Approve and merge

Before pushing a fix or a conflict resolution, review only the fix commits
and any conflict resolutions per
when-to-run.md Scope, not the whole
pull request, unless the user asks.
Before a fix that will be pushed, pause and later restore auto-merge per
auto-merge-pause.md. Otherwise let an enabled
auto-merge finish. Before any approval or manual merge, read
merge.md. Without --merge or auto-merge, a passing
pull request is complete; report it as ready.

Clean up task resources

On every exit path, follow
task-resources.md. Remove only
worktrees this invocation created, never a pre-existing one. Keep a repository
watcher running while other selected pull requests in that repository still need
it. Keep task-created worktrees while their pull requests remain open, including
review or policy blockers; after merge or closure, or on explicit cleanup, use
the worktree skill's Remove section and report retained paths and blockers.

Report

End with one line per pull request: URL, author, head SHA, state, blocker or
completed action, and next step. State whether it waits on CI, a reviewer, an
author, repository policy, or the user. Include check-run URLs when available.
Report each removed worktree and local branch, or its exact retention blocker.