From 2432a5792d600159e5d7578ed6537b8938df0483 Mon Sep 17 00:00:00 2001 From: Luke Curley <432854+kixelated@users.noreply.github.com> Date: Wed, 28 Oct 2026 09:41:06 -0700 Subject: [PATCH] docs(complete): a blanket answer picks every recommendation "Use your recommendations" is a blank check, /quest-merge included. Only a recommendation that settles a decision the user hasn't seen still needs its own question. Co-Authored-By: Claude Opus 5.5 --- assets/skills/complete.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/skills/complete.md b/assets/skills/complete.md index 6d37022f..0795e0ab 100644 --- a/assets/skills/complete.md +++ b/assets/skills/complete.md @@ -20,7 +20,7 @@ Ask synchronously with one question per PR, never grouping PRs into one question Include a brief summary of each PR. Act on a PR only after the user picks its action in this session, including PRs found on a later refresh. -A blanket answer, such as "accept all" or "use your recommendations", never picks `/quest-merge`; ask again for each PR it would merge. +A blanket answer, such as "accept all" or "use your recommendations", picks your recommendation for every PR in scope, `/quest-merge` included, except a PR whose recommendation settles a decision you have not yet shown; ask about those. A skip or hold stands until the user lifts it: do not ask about that PR again on a refresh, and state the hold in every sub-agent brief for it. GitHub auto-merge is that pick: enabling it takes write access, and GitHub disables it when anyone without write access pushes. Do not ask about a PR with auto-merge enabled; leave it to land, and dispatch `/quest-merge` only when a conflict, failing check, or review finding stalls it.