Skip to content

docs(complete): a blanket answer picks every recommendation #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kixelated merged 2 commits into from
Oct 28, 2026
Merged

docs(complete): a blanket answer picks every recommendation #262

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2432a57
docs(complete): a blanket answer picks every recommendation
kixelated Oct 28, 2026
aab412e
Merge remote-tracking branch 'origin/main' into quest-complete/blanke…
kixelated Oct 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion assets/skills/complete.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading