Repository navigation
feat(skills): /quest-merge queues inline or sends the PR to /quest-iterate - #292
Merged
Merged
Conversation
kixelated
marked this pull request as ready for review
October 30, 2026 16:16
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
…erate (#292) * quest: plan merging through a host gate Inline merge picks, small batches landed from the maintainer's host, and an asynchronous Codex fixer for ejected batches instead of bisection. * feat(skills): /quest-merge queues inline or sends the PR to /quest-iterate /quest-merge no longer runs in a sub-agent that fixes, waits, and lands. It checks that a counted review names the head, with no open findings, passing checks, and no conflict, then queues it with `quest merge --land`; otherwise it recommends /quest-iterate. /quest-complete and /quest-spawn run it inline and recommend /quest-iterate for PRs whose head has no counted review. * fix(skills): merge releases its hold on every handoff and fetches before quest check * chore(quest): claim quest/m0/host-land/inline-merge.md Quest-Claim: 72896b8d938dce87 * quest: finish inline-merge * fix(skills): merge ignores the gate's own quest land check * feat(skills): plan follow-ups at queue time, one /quest-plan per follow-up Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
moq-bot
Bot
force-pushed
the
quest/m0/host-land/inline-merge
branch
from
October 30, 2026 16:51
49f47d6 to
46472ba
Compare
kixelated
added a commit
that referenced
this pull request
Nov 1, 2026
The guide's follow-up rule now says the interview lets the user drop a follow-up and that the caller plans a background agent's follow-ups the same way, so complete.md no longer repeats it. #292 already made merge, complete, and spawn plan follow-ups without offering; this finishes the quest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
moq-bot Bot
pushed a commit
that referenced
this pull request
Nov 1, 2026
* chore(quest): claim quest/m0/helpers/follow-up-plan.md Quest-Claim: 30da3116cb3d0191 * docs(guide): one rule for planning a delegated agent's follow-ups The guide's follow-up rule now says the interview lets the user drop a follow-up and that the caller plans a background agent's follow-ups the same way, so complete.md no longer repeats it. #292 already made merge, complete, and spawn plan follow-ups without offering; this finishes the quest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: moq-bot <moq-bot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Finishes inline-merge from the host-land epic. Picking a PR to merge no longer starts a sub-agent that fixes the PR, waits on CI, and lands it.
Behavior
/quest-mergeruns inline. It takes the hold, readsquest statusonce, and queues the head withquest merge --landwhen all of these hold:## Reviewrecord names the head, or the guide's exemptions cover the changes since it;quest landcheck;quest check --basepasses on the fetched head.Otherwise it releases the hold and recommends
/quest-iterate, saying what's missing. It never fixes, pushes, or waits. While checks are only pending, it reports that the pick stands./quest-complete: runs/quest-mergeinline, and runs only/quest-reviewand/quest-iteratein sub-agents./quest-iteratefor any PR whose head has no counted review./quest-iteratewithout asking, then merges inline when it reports. That includes after amerge_conflictorfailed_checksejection.checks_pending, it merges again on a later refresh./quest-spawn: offers the same options and runs merges inline the same way.Follow-ups (user, 2026-10-30):
/quest-mergeplans a PR's suggested follow-ups as soon as it's queued, as if the PR lands, without waiting for the merge./quest-completeand/quest-spawnbatch them at the end. The guide now says to plan recommended follow-ups without offering first, one/quest-planrun per follow-up.The README skill table and getting-started describe the new
/quest-merge.Choices made without asking
quest check --basestays in/quest-merge. The plan said the gate's check covers it, but CI runsquest checkwithout--base, so the gate would miss a PR that leaves its quest stale. On a finding, merge now recommends/quest-iterateinstead of fixing the PR itself.checks_pending, so/quest-mergereports that the pick stands, and/quest-completeretries on a later refresh. The host daemon can drop this requirement, since it runs the check itself.Overlaps
#288 and #276 edit the same skills. Whichever lands second reconciles.
Checks
just checkpassed.just testpassed: 626 + 426 tests. It was run withCLAUDE_CONFIG_DIR/QUEST_WORKTREE_HOMEunset andGIT_CONFIG_GLOBAL=/dev/null. On this host,test/review.test.tsotherwise fails: its fixture commits under my global SSH commit signing withoutssh-keygenon its PATH. That's an environment gap, not caused by this change.Review
quest review --base origin/main, round 3 of session01a18d98merge.md:21): requiring every required check would block on the gate's unreportedquest landcheck. Fixed.quest check. Both fixed.Suggested follow-ups
test/review.test.ts(andagent.test.ts) should isolate themselves from the caller's global git and Claude config.🤖 Generated with Claude Code
(written by Claude Opus 5.5)