merge-issues

Merges duplicate and subset GitHub issues queued on shared eval snapshots.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill merge-issues-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-issues
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/merge-issues
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill merge-issues-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Open issue backlogs accumulate duplicates, subsets, and small related edits filed weeks apart on the same skill's eval snapshot, and each one pays its own expensive evaluation run. This Skill finds those piles by computing per-slot queue depth and merges N-way where the issues are genuinely one piece of work, buying back evaluation runs. ## Core Features & Use Cases - Queue computation: Runs slots.py against GitHub project board, open issue, and open PR data to rank eval slots by queue depth and flag coverage gaps. - Four merge verdicts: Classifies groups as duplicate, absorb (strict subset), batch (one-sitting edits), or split-the-lanes, with evidence gathered by opening the cited files. - Approved application only: Proposes partitions first, then folds content, retitles targets, moves assignees and labels, and closes losers with reasoning after lead approval. - Use Case: A repo lead asks to "merge the backlog" before promoting work; the Skill reads every deep queue, proposes a partition of fifteen issues into four groups, and reports how many evaluation runs the merges buy back. ## Quick Start Ask the assistant to merge the backlog by computing the eval-slot queues and proposing which open issues should be combined.

Frequently Asked Questions about merge-issues

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

FAQPage Schema
How do I find duplicate GitHub issues in a large backlog?▼

Compute per-slot queue depth with slots.py against the project board and open issues, then read every deep queue at once. Prove duplication by opening the files both issues cite and confirming the fix is the same edit to the same lines, not by comparing titles.

How to merge multiple GitHub issues into one?▼

Fold each source issue's content into the target under a dated heading, retitle the target if scope changed, move assignees and labels, then close each loser with a comment naming what the issues share. Merge N-way as a partition rather than pairwise.

When should issues sharing the same files not be merged?▼

Sharing a snapshot alone is never a reason to merge. Keep issues apart when one is blocked, when one person cannot finish the combined work in one sitting, or when a needs-decision label has no ruling while the other issue is startable.

Does this Skill close or edit issues automatically?▼

No. It proposes a partition with per-group evidence and waits for lead approval before applying anything. It never starts the work the issues describe and never writes the project board, since closing an issue auto-moves its card.

Why does the queue output miss some open issues?▼

Issues without a Touches line reach no queue, and issues in no rendered section are invisible to the script. The coverage block at the bottom lists both buckets by number so they can be read by hand.