shift

Shift

One pass over the tracker with nobody watching. The state lives on GitHub, in labels, never in a file: a shift that runs twice does its work once.

Input

$ARGUMENTS

• --max <n>: issues dispatched this pass. Default 2, for cost.
• --dry-run: print each action in place of taking it. No comment, no label, no worker, no landing.

Protocol

1. Labels. gh label list --limit 100. Create the ones it does not list: needs-info, dispatched, blocked for issues; needs-human for both; shift, tier:low, tier:human, land-ok for PRs.

   gh label create needs-info --description "Missing evidence or acceptance criteria"
   gh label create needs-human --description "Waits for the human"
   gh label create tier:low --description "Lands on green checks without a human"
   gh label create tier:human --description "Waits for the human's land-ok"
   gh label create land-ok --description "The human's ok on the pull request's change"
   

2. Triage. gh issue list --state open --search "-label:needs-human sort:created-asc" --limit 100 --json number,title,labels,createdAt: an issue labelled needs-human waits for the human, and the search leaves it out, so a pile of them never crowds older issues out of the list; past 100, the newest wait for a later pass. Drop the ones already labelled dispatched, blocked, needs-info, epic or needs-human: the search index can lag a label added moments ago. Oldest first, bug before the rest. Read ${CLAUDE_PLUGIN_ROOT}/skills/triage/SKILL.md and apply its protocol to each: it verifies the issue against the current code and closes or comments as its verdict fixes. Read it, do not invoke it: github-flow:triage is a manual skill. unclear → label needs-info. valid → candidate.

3. Dispatch. The first --max candidates, in one call to github-flow:dispatch with their numbers.

4. Maintain. gh pr list --state open --label shift --json number,url,headRefName,headRefOid,mergeable,statusCheckRollup,reviewDecision,comments,labels. Skip the ones labelled needs-human: two fix rounds were not enough.

   • Fix. A PR with a red check, mergeable: CONFLICTING, or an unanswered comment goes to one worker in fix <pr> mode: ${CLAUDE_PLUGIN_ROOT}/skills/dispatch/references/worker-brief.md filled as github-flow:dispatch fills it, in a general-purpose subagent, model: opus and isolation: worktree on the call. A comment counts only when its authorAssociation is OWNER, MEMBER or COLLABORATOR and its first line is no <!-- … --> marker. Count the PR's comments whose first line is <!-- shift-fix --> first: at two, label needs-human and leave the PR alone.
   • Land. A PR no worker took this pass, labelled tier:low or land-ok, its checks green, mergeable: MERGEABLE, no comment unanswered. Its own worker is done: dispatch adds shift only once the worker reported, and a fix worker never lands. Run the land command of .claude/github-flow.json on its branch with Bash run_in_background, and read its last line in the task notification. With no land command, every PR waits for the human, who lands it with /github-flow:await-merge.

5. Record a blocked fix. A fix worker posts its own <!-- shift-fix --> comment. One that reports blocked does not: post it, written to a file outside the repository, with gh pr comment <pr> --body-file <tmp>, first line <!-- shift-fix -->, then the first line of the failure. Step 4 counts these comments; without them the 2-attempt bound never fires.

6. Digest. The report is the deliverable.