How do I install the Github Issue Dedupe skill?

Run npx skillmds@latest add greenmamba29/github-issue-dedupe in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Github Issue Dedupe skill do?

Is Github Issue Dedupe safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Issue Dedupe?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Issue Dedupe free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Issue Dedupe?

Greenmamba29 (@greenmamba29) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Issue Dedupe by greenmamba29

Name: Github Issue Dedupe
Author: Greenmamba29

File contents

name	description	license	tags
github-issue-dedupe	Detect and consolidate duplicate GitHub issues using semantic similarity matching. Identifies duplicate reports, posts linking comments, closes duplicates, and keeps a canonical issue updated with all relevant context.	MIT	--- github issues deduplication automation project-management

GitHub Issue Dedupe

Overview

Automatically detect duplicate GitHub issues using semantic similarity, link them together, close duplicates with a reference comment, and maintain a canonical issue with consolidated context.

When to Use

When your issue tracker has grown large with many potential duplicates
Before a sprint planning session to clean up the backlog
After a major release when bug reports flood in
When you want to prevent duplicate effort on the same problem
When enforcing issue hygiene across a public open-source project

Instructions

Fetch all open issues: gh issue list --state open --limit 500 --json number,title,body,labels.
Build a similarity matrix:
- Tokenize titles and bodies, remove stop words.
- Compute cosine similarity between all issue pairs.
- Flag pairs exceeding DUPLICATE_THRESHOLD as potential duplicates.
For each duplicate cluster:
- Identify the canonical issue (oldest or highest vote count).
- Review pairs above threshold to confirm semantic similarity.
- Post comment on duplicate: "Duplicate of # - closing in favor of original."
- Close duplicate with label duplicate.
- Update canonical issue body with any unique details from duplicates.
Handle false positives: skip pairs where titles differ by key identifiers (version numbers, OS, component).
Return deduplication report: total issues scanned, duplicates found, clusters merged.

Environment

DUPLICATE_THRESHOLD=0.82
BATCH_SIZE=100
DRY_RUN=false
SKIP_LABELS=wontfix,known-issue
MERGE_COMMENTS=true

Examples

Input:

repository: org/my-app
state: open
limit: 200

Output:

Deduplication Report
Issues scanned: 187
Duplicate clusters found: 14
Issues closed: 23
Sample merges:
- #445, #467, #489 -> canonical: #445 ("Login button not working")
- #312, #398 -> canonical: #312 ("PDF export fails on Safari")
False positives skipped: 3

---name: github-issue-dedupedescription: | name | description | license | tags |---| name | description | license | tags ||------|-------------|---------|------|| github-issue-dedupe | Detect and consolidate duplicate GitHub issues using semantic similarity matching. Identifies duplicate reports, posts linking comments, closes duplicates, and keeps a canonical issue updated with all relevant context. | MIT | --- github issues deduplication automation project-management |# GitHub Issue Dedupe## OverviewAutomatically detect duplicate GitHub issues using semantic similarity, link them together, close duplicates with a reference comment, and maintain a canonical issue with consolidated context.## When to Use- When your issue tracker has grown large with many potential duplicates- Before a sprint planning session to clean up the backlog- After a major release when bug reports flood in- When you want to prevent duplicate effort on the same problem- When enforcing issue hygiene across a public open-source project## Instructions1. Fetch all open issues: `gh issue list --state open --limit 500 --json number,title,body,labels`.2. Build a similarity matrix: - Tokenize titles and bodies, remove stop words. - Compute cosine similarity between all issue pairs. - Flag pairs exceeding DUPLICATE_THRESHOLD as potential duplicates.3. For each duplicate cluster: - Identify the canonical issue (oldest or highest vote count). - Review pairs above threshold to confirm semantic similarity. - Post comment on duplicate: "Duplicate of #<canonical> - closing in favor of original." - Close duplicate with label `duplicate`. - Update canonical issue body with any unique details from duplicates.4. Handle false positives: skip pairs where titles differ by key identifiers (version numbers, OS, component).5. Return deduplication report: total issues scanned, duplicates found, clusters merged.## Environment```DUPLICATE_THRESHOLD=0.82BATCH_SIZE=100DRY_RUN=falseSKIP_LABELS=wontfix,known-issueMERGE_COMMENTS=true```## Examples**Input:**```repository: org/my-appstate: openlimit: 200```**Output:**```Deduplication ReportIssues scanned: 187Duplicate clusters found: 14Issues closed: 23Sample merges:- #445, #467, #489 -> canonical: #445 ("Login button not working")- #312, #398 -> canonical: #312 ("PDF export fails on Safari")False positives skipped: 3```

Frequently asked questions

Github Issue Dedupe