Repository navigation
Conversation
Waiting for the merge itself leaves issues silent for as long as the queue takes, though the plan is settled once the PR is queued. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
kixelated
left a comment
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: e962c04
No actionable bugs found in assets/skills/import.md. Moving the issue update to queue entry gives reporters the settled decision and tracking PR sooner, without changing the planning interview or making the planning PR close the issue. This narrow timing change is simpler than waiting on a separate queue monitor; a queued plan is still pending, not already landed.
Verification limits: static inspection of the complete skill and PR discussion only. I did not execute an import or exercise queue success/failure behavior.
Problem
/quest-importcomments on each issue with its tracking quest only once the planning PR merges. Behind a merge queue that leaves the issues without a quest pointer for as long as the queue takes, even though the plan was settled when the PR was queued.Approach
Post the comment when the merge starts: when the PR enters the merge queue, or when it merges if the repository has no queue.
Impact
This changes only skill wording.
🤖 Generated with Claude Code
(Written by Claude Opus 5.5)