merge-recent-issues

Checks recently filed GitHub issues against the open backlog for duplicate merges.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New issues filed in the last couple of days often duplicate work already tracked in the backlog, and catching them late means wasted ranking, promotion, and assignment effort. This Skill runs a daily pass that compares each new issue against the open pool and proposes merges before duplicates decay. ## Core Features & Use Cases - Windowed duplicate detection: Reads every issue filed in a configurable day window (default 2 days, e.g. /merge-recent-issues 5) and compares each against Backlog, unassigned Ready, and icebox items via gh CLI. - Doctrine-driven verdicts: Delegates merge verdicts (duplicate, absorb, batch, lane split) to the /merge-issues skill and applies them verbatim, never inventing its own rules. - Evidence-based proposals: Opens the files both issues name, verifies fix sites, blocker state, and eval-run cost before proposing, then applies only lead-approved merges by folding content, retitling, moving assignees/labels, and closing with reasoning. - Use Case: After /triage-standup files the day's inflow, run this Skill to catch a Friday-afternoon issue that duplicates an existing backlog card before it gets ranked and assigned. ## Quick Start Run /merge-recent-issues to check the last two days of new issues against the open backlog and propose any merges for approval.

Frequently Asked Questions about merge-recent-issues

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

FAQPage Schema
How do I check new GitHub issues for duplicates against the backlog?▼

Run /merge-recent-issues to list every issue filed in the last two days and compare each against Backlog, unassigned Ready, and icebox items. It proposes merges with evidence and applies only what you approve.

How do I change the time window for recent issue checks?▼

Pass a day count to the command, such as /merge-recent-issues 5, to check issues filed in the last five days. The default window is two days, and windows intentionally overlap so no issue is ever skipped.

What is the difference between merge-recent-issues and merge-issues?▼

merge-recent-issues owns selection and cadence, checking only issues filed in the last few days. merge-issues owns the merge doctrine and verdicts, which this skill reads and applies verbatim rather than re-deriving.

Can this skill merge a new issue into work already in progress?▼

No. It never merges into In Progress, Review, or assigned Ready cards. If a new issue duplicates active work, it closes the new one as a duplicate of active work and comments pointing at the active card.

Does the skill apply merges automatically without approval?▼

No. It proposes merges first and applies only what the lead approves. It has no Edit or Write tool, creates no branches or PRs, and never writes the project board.