github-issue-dedupe

To find duplicate GitHub issues automatically, use this Skill to perform semantic search and keyword matching. It gathers issue context, compares potential duplicates, and identifies matches based on shared root causes and symptoms.

Semantic duplicate detection works by extracting issue context, performing multi-strategy searches via the GitHub CLI, and comparing root causes alongside symptoms to surface high-confidence duplicate matches.

Yes, you can automate GitHub issue triage to consolidate duplicate reports. The Skill runs a deduplication workflow using your GitHub token to analyze new issues and optionally post findings as comments.

Yes, you need the GitHub CLI to detect duplicate issues semantically. The Skill relies on the gh command-line tool to execute multi-strategy searches and surface similar issues by keywords and error patterns.

The best way to compare root causes when triaging GitHub issues is to extract issue context like titles and bodies, run multi-strategy keyword searches, and evaluate matching symptoms to determine actual duplication.

To comment on a GitHub issue after finding a duplicate, the Skill determines duplication confidence based on root cause comparison and optionally posts the high-confidence findings directly to the target issue.