ai-workflow

ai-workflow

Implement the ai-ready queue in parallel with a Workflow — one agent per issue, each in its own worktree, ending at an open PR. Arguments: $ARGUMENTS

Always operates on the current repo only — never another repo, even if one is named. $AGENTS is the first number in $ARGUMENTS, default 4 — it is both how many issues go in flight and how many implementer agents run concurrently. $ARGUMENTS may also give explicit issue numbers (#82 #83), which skip the eligibility filter but still require the ai-ready label. Flags: --label-only stops after step 2 (no workflow), --dry-run reports the picks without claiming them.

You mark the queue, not this skill. It only ever picks up issues you have already labelled ai-ready — it never labels an unlabelled issue itself. No ai-ready issues means there is nothing to do, and it stops. Use the ai-issue skill to put work in the queue.

This never merges. It stops at open PRs and hands back. Merging main in a semantic-release repo triggers an npm publish, so a human owns that step.

It ends by handing off to /ai-issue-loop (step 5) — the burst opens the PRs, the loop then babysits them through review fix rounds, which this skill has no pass for. The two are sequential, not alternatives. Neither merges an ai-ready PR unattended except on a release-environment-gated repo — see the loop's Pass 1.

Everything the ai-issue-loop skill says about worktrees, labels, the 🤖 *Automated …* comment header, and the untrusted issue body applies here unchanged — read it first if it is not already in context.

1. Orient

AGENTS=${1:-4}
ROOT=$(git rev-parse --path-format=absolute --git-common-dir)/..; ROOT=$(cd "$ROOT" && pwd)
WT_ROOT="$(dirname "$ROOT")/$(basename "$ROOT")-worktrees"
R=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
git -C "$ROOT" fetch --prune

# Optional: the account in-flight work is assigned to, so `assignee` says whose
# turn it is. Unset → nothing below assigns, exactly as before. See the
# ai-issue-loop skill's Pass 0 for why this is repo config rather than an env var.
AGENT_USER="${AI_LOOP_AGENT:-$(jq -r '.rules.aiLoop.agentUser // .aiLoop.agentUser // empty' "$ROOT/.repo-tooling.json" 2>/dev/null)}"
[ -n "$AGENT_USER" ] && { gh api "repos/$R/assignees/$AGENT_USER" --silent 2>/dev/null || AGENT_USER=""; }