land-tasqx-prlisted

# Land a tasqx task PR `main` in tasqx is protected: pull request required, linear history, twelve required status checks, no force pushes. Auto-merge is on and open review threads do not block a merge (both since 2026-09-18), so nobody waits on CI: steps 1–3 arm the PR and the session moves on to the next task, and steps 4–7 run at the next task boundary. It assumes the task branch `task/<id>-<slug>` lives in a worktree under `~/projects/worktrees/tasqx/` and has passed the review in `CLAUDE.md` ("One task, one branch, one builder, one review"). Work through the steps in order — earlier runs each lost time to skipping or reordering one of them (see "Why this order" at the end). ## Steps Two helpers ship with this skill, in `.claude/skills/land-tasqx-pr/scripts/` (`$S` below). They exist because a session that entered the task worktree with `EnterWorktree` is isolated to it, and the isolation guard refuses an inline `gh api graphql … --jq` with nested quotes, a `$(cat …)` inside `gh` arguments, and chained commands as "too complex to verify": - `$S/open-pr.sh <branch> <title-file> <body-file>` opens the PR with the title and body read from files, so an apostrophe or backtick in the commit subject cannot break or expand the command. - `$S/wait-qodo.sh <n>` waits until Qodo has commented and nothing of its is still "busy", then lists the unresolved threads (every page); `$S/wait-qodo.sh <n> --bodies` prints each one's finding as text. Exit 3 means Qodo had not fi