Menu
Merge approved PRs in safe batches — checks CI, fixes policy failures, handles conflicts, ratchets corpus after parser merges.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Load perl-lsp coding standards for code-writing or code-review work in this repo. Use when implementing, fixing, reviewing, or validating code.
Run a TDD parser-fix workflow for perl-parser-core or related parser crates. Use when a parser bug has a concrete failing construct and needs tests, a minimal fix, and verification.
Turn a discovery into a builder-ready handoff packet. Use when a scout or coordinator has identified a concrete slice and needs exact scope, verification, and routing rather than code changes.
Research-first workflow that scouts exact scope before launching a constrained builder. Use when a feature or fix is too unconstrained for a direct builder — converts ~50% success into ~90% by eliminating implicit decisions.
Load roadmap weighting for scouts and coordinators so slices are ranked by actual repo priorities instead of convenience.
Load shared swarm behavioral rules for coordinators and workers. Use for task routing, receipts, direct messaging, dedup, worktree boundaries, and lifecycle discipline.
| name | merge-queue |
| description | Merge approved PRs in safe batches — checks CI, fixes policy failures, handles conflicts, ratchets corpus after parser merges. |
| user-invocable | true |
| argument-hint | <PR numbers or 'all'> [--dry-run] |
Merge approved PRs safely in batches. Focus: $ARGUMENTS
Verify master CI is green before starting:
gh run list --branch master --limit 1 --json status,conclusion
If the latest run is not completed/success, stop — do not merge onto a red master.
Build the merge list:
$ARGUMENTS is all: gh pr list --state open --json number,title,mergeable,reviewDecision --limit 100$ARGUMENTSmergeable == "MERGEABLE" and checks are passingFor each PR in priority order:
Check all CI checks are green:
gh pr checks <num>
If policy_checks fails (stale CURRENT_STATUS.md):
git fetch origin && git checkout <branch>
python3 scripts/update-current-status.py
git add docs/project/CURRENT_STATUS.md
git commit -m "chore: refresh computed metrics"
git push
Then re-check CI. If it still fails, skip this PR.
If merge conflicts exist:
git fetch origin
git checkout <branch>
git rebase origin/master
git push --force-with-lease
Only rebase when there are actual conflicts. Do NOT rebase clean PRs — unnecessary rebases burn CI queue capacity and cancel in-flight runs.
If CI is red for other reasons: skip this PR and continue to the next. Never merge red.
Merge in batches of 3:
gh pr merge <num1> --merge
gh pr merge <num2> --merge
gh pr merge <num3> --merge
After each batch, wait for master CI to complete:
gh run list --branch master --limit 1 --json status,conclusion
Poll every 30 seconds until status == "completed". If conclusion != "success",
stop the queue — do not merge more PRs onto a red master.
After merging parser fix PRs, ratchet the corpus baseline to lock in gains:
just cpan-corpus-ratchet
If the ratchet updates the manifest, commit and push to master.
After all merges complete, report:
--dry-run mode: If $ARGUMENTS contains --dry-run, report what would
be merged without actually merging. Useful for pre-flight review.