void-merge

Merges open pull request queues by unblocking order with green, up-to-date CI checks.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-merge-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-merge
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-merge
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-merge-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a queue of open pull requests by hand is error-prone: merging in the wrong order creates conflicts, merging a branch that is behind its base invalidates CI results, and resolving generated artifacts by picking a side corrupts them. This Skill drains a PR queue safely without breaking the repository. ## Core Features & Use Cases - Unblocking-based ordering: Orders PRs by which one removes the cause of another's conflict, never by date or number. - Strict merge conditions: Requires all checks green, the branch up to date with its base, and a clean merge before merging, re-running CI after any update. - Conflict classification: Regenerates mechanical conflicts (generated artifacts) from merged sources and hands content conflicts back to their author. - Use Case: After a sprint, ten reviewed PRs are open against main, several conflicting. Use this Skill to merge them in the correct order, regenerate lockfiles and catalogs, and report the exact blocking reason for any PR that cannot merge. ## Quick Start Merge all open pull requests targeting the main branch, ordering them by dependency and reporting any that remain blocked.

Frequently Asked Questions about void-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge multiple open pull requests in the right order?

Order pull requests by unblocking relationships rather than date: a PR whose content removes the cause of another's conflict merges first, then those with the fewest conflicts. Re-evaluate the queue after each merge since every merge makes remaining PRs behind.

Why is a green CI pull request with BEHIND status not safe to merge?

A BEHIND status means the checks ran against a base state that no longer exists, so green results are stale. Update the branch with its base, wait for CI to run again, and only then merge.

How should merge conflicts in generated files be resolved?

Regenerate the artifact from the merged sources instead of picking one side. Choosing a side passes CI but leaves the artifact inconsistent with its sources. If the generated file also carries a content decision, treat it as a content conflict for a human.

Can this Skill bypass branch protection or force-merge a failing PR?

No. It never uses admin overrides, never force-pushes protected branches, and never merges a PR with a failing check. Branch protection is treated as the authoritative guardrail, and blocked PRs are reported with their exact blocking reason.

Does this Skill review code quality before merging?

No. It assumes every PR entering the queue has already been reviewed by a human and decides only merge mechanics, never quality. It does not read diffs to judge the code.