What
WS1 — Make high-traffic skills stop rubber-stamping deterministic decisions and fill invocation gaps.
Part of the input-reduction epic.
Why
Every single-item invocation of the lifecycle skills fires an AskUserQuestion to pick solo vs. team execution — but the recommendation is already computed deterministically from size labels / commit counts / failure counts, and --solo/--team overrides already exist. The user is confirming a machine choice with no new information. Similar gaps: sonar-fix needs a PR number that ci-fix already auto-detects; memory-review is missing from the alias table; CI-timeout asks a question precisely when the user has likely walked away.
Where
global/skills/_internal/issue-work/SKILL.md (mode select ~:214; CI timeout ~:463-466)
global/skills/_internal/pr-work/SKILL.md (mode select ~:283)
global/skills/_internal/release/SKILL.md (mode select ~:157)
global/skills/_internal/doc-review/SKILL.md (mode select ~:127)
global/skills/_internal/implement-all-levels/SKILL.md (mode select ~:53)
global/skills/_internal/sonar-fix/SKILL.md (require <pr-number>)
global/CLAUDE.md (alias table — memory-review row missing)
How
- Auto-mode: when the mode signals are unambiguous (single-direction, e.g.
size/XS → solo), apply the recommended mode silently and print a one-line notice: [Mode: solo — XS issue; pass --team to override]. Fire AskUserQuestion ONLY when signals genuinely conflict. --solo/--team keep working.
- sonar-fix auto-detect: if no PR number is given, resolve via
gh pr list --head "$(git branch --show-current)" --json number -q '.[0].number' (mirror ci-fix).
- memory-review alias: add a row to the Skill Aliases table in
global/CLAUDE.md.
- CI timeout default: on the 10-minute polling limit, default to "leave PR open" + print the resume command (
pr-work <PR>); ask only with an explicit --wait-on-timeout opt-in.
Acceptance criteria
Labels: type/feature, size/S
Part of #743
What
WS1 — Make high-traffic skills stop rubber-stamping deterministic decisions and fill invocation gaps.
Part of the input-reduction epic.
Why
Every single-item invocation of the lifecycle skills fires an
AskUserQuestionto pick solo vs. team execution — but the recommendation is already computed deterministically from size labels / commit counts / failure counts, and--solo/--teamoverrides already exist. The user is confirming a machine choice with no new information. Similar gaps:sonar-fixneeds a PR number thatci-fixalready auto-detects;memory-reviewis missing from the alias table; CI-timeout asks a question precisely when the user has likely walked away.Where
global/skills/_internal/issue-work/SKILL.md(mode select ~:214; CI timeout ~:463-466)global/skills/_internal/pr-work/SKILL.md(mode select ~:283)global/skills/_internal/release/SKILL.md(mode select ~:157)global/skills/_internal/doc-review/SKILL.md(mode select ~:127)global/skills/_internal/implement-all-levels/SKILL.md(mode select ~:53)global/skills/_internal/sonar-fix/SKILL.md(require<pr-number>)global/CLAUDE.md(alias table —memory-reviewrow missing)How
size/XS→ solo), apply the recommended mode silently and print a one-line notice:[Mode: solo — XS issue; pass --team to override]. FireAskUserQuestionONLY when signals genuinely conflict.--solo/--teamkeep working.gh pr list --head "$(git branch --show-current)" --json number -q '.[0].number'(mirrorci-fix).global/CLAUDE.md.pr-work <PR>); ask only with an explicit--wait-on-timeoutopt-in.Acceptance criteria
sonar-fixresolves PR from current branch when arg omitted.memory-reviewappears in the alias table.--solo/--teamoverride semantics.Labels:
type/feature,size/SPart of #743