/gaia-residue

name: gaia-residue
description: Triage drain over the keyed audit residue recorded in merged pull-request bodies. Enumerates candidates, resolves each one's cited line, and takes one disposition per entry, promote to a tech-debt issue, dismiss, or keep. Never fixes anything. Pass `list` to see live candidates or `why <path>:<line>` to explain one.
argument-hint: [review|list|why <path>:<line>|<path>:<line>]

Run the GAIA **residue** workflow with these arguments: `$ARGUMENTS`

Pre-flight: Worktree check

This command publishes a branch and a pull request from a repo-wide read of every merged pull request. If invoked from a linked worktree, reject hard: `gaia_refuse_if_worktree` (`.gaia/scripts/main-only-lib.sh`) asks the shared resolver which tree this is and refuses out loud, naming the main checkout, when the answer is a worktree.

Detection (run this first, before anything else):

. .gaia/scripts/main-only-lib.sh
gaia_refuse_if_worktree "/gaia-residue" || exit 1

If the detection does not fire, fall through to the workflow dispatch line below.

Read `.claude/skills/gaia/references/residue.md` from the project root and follow it exactly. That reference is written to consume an argument string, treat the arguments above as that input (the leading token selects the subcommand: `review`, `list`, or `why <path>:<line>`; an argument string that is nothing but a bare `<path>:<line>` coordinate explains that candidate directly). If no arguments were provided, follow the reference's no-argument path (which defaults to `review`).