gh-deduplicate-issues

Closes duplicate GitHub issues via gh and jq, preserving the oldest issue.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-deduplicate-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-deduplicate-issues
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude-plugin/skills/gh-deduplicate-issues
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-deduplicate-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines GitHub issue management by automatically identifying and closing duplicate issues, reducing backlog clutter and improving focus on unique problems.

Core Features & Use Cases

  • Duplicate Identification: Groups issues with similar intent, even with slightly different wording.
  • Automated Closure: Comments "Duplicate of #XXXX" and closes duplicate issues, keeping the oldest as the canonical survivor.
  • Use Case: When a repository has many issues reporting the same bug or feature request across different sessions, this skill consolidates them into a single, actionable item.

Quick Start

Use the gh-deduplicate-issues skill to close duplicate GitHub issues in the OWNER/REPO repository, keeping issue #3962 as the survivor for issues related to ADR-009 compliance.

Frequently Asked Questions about gh-deduplicate-issues

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

FAQPage Schema
How do I automatically close duplicate GitHub issues in my repository?

You can automatically close duplicate GitHub issues by grouping similar issues, commenting "Duplicate of #XXXX" on them, and closing them while preserving the oldest issue as the canonical survivor to reduce backlog clutter.

What is the best way to identify duplicate issues when they have slightly different wording?

Identifying duplicate GitHub issues with different wording is handled by grouping issues with similar intent, allowing the deduplication process to consolidate them into a single actionable item automatically.

Do I need the GitHub CLI and jq to close duplicate issues automatically?

Yes, you need the GitHub CLI (`gh`) for issue manipulation and `jq` for JSON parsing to automate the closure of duplicate GitHub issues in your repositories.

How do I consolidate multiple bug reports across different sessions into a single GitHub issue?

To consolidate multiple bug reports, the deduplication process groups issues reporting the same bug or feature request, closes the duplicates with a reference comment, and keeps the oldest issue as the canonical survivor.

Can I preserve the oldest issue as the canonical survivor when closing duplicate GitHub issues?

Yes, when closing duplicate GitHub issues, the process automatically preserves the oldest issue as the canonical survivor and comments on the closed duplicates indicating which issue they duplicate.

Why should I use automated issue deduplication for repositories with numerous similar issues?

Automated issue deduplication reduces backlog clutter and improves issue tracking efficiency by consolidating numerous similar GitHub issues into single, actionable items, saving manual triage effort.