skills.rest
chagong
chagongCOMMUNITY
Explore all skills by this author →
GitHub

find-duplicates

Identify duplicate GitHub issues using semantic similarity and confidence scoring.

1|2|Updated Dec 17, 2025
Search Tags:#code review#github#issues#triage#bug tracking#duplicates
One-click install
npx skills add https://github.com/chagong/IssueLens --skill find-duplicates-chagong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-duplicates
Source: https://github.com/chagong/IssueLens/tree/main/.github/skills/find-duplicates
Command: npx skills add https://github.com/chagong/IssueLens --skill find-duplicates-chagong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain a clean and organized issue tracker by automatically identifying and flagging potential duplicate issues, saving developers time and preventing redundant work.

Core Features & Use Cases

  • Duplicate Detection: Compares a target issue against existing ones using semantic similarity, error patterns, and component matching.
  • Confidence Scoring: Assigns a confidence level (High, Medium, Low) to potential duplicates.
  • Use Case: When a new bug report comes in, use this Skill to quickly check if it's a re-report of an existing issue, linking to the original and suggesting closure if it's a high-confidence match.

Quick Start

Find duplicate issues for issue number 123 in the repository owner/repo.

Frequently Asked Questions about find-duplicates

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

FAQPage Schema
How do I find duplicate GitHub issues in my repository?▼

To find duplicate GitHub issues, compare a target issue against existing ones using semantic similarity, error patterns, and reproduction steps. This process scopes analysis to a specific repository, checking both open and closed issues within a 90-day window to flag potential duplicates.

How does duplicate issue detection handle error messages and stack traces?▼

Duplicate issue detection evaluates error messages and stack traces by comparing them against existing reports for matching patterns. It uses these technical details alongside semantic similarity and reproduction steps to prioritize high-confidence matches and streamline bug tracking triage.

Can I check for duplicate bugs in closed GitHub issues?▼

Yes, you can check for duplicate bugs in closed GitHub issues. The analysis considers both open and closed issues within a 90-day window, ensuring that previously resolved bug reports are factored into the duplicate detection and confidence scoring process.

What is the best way to prioritize GitHub issue triage for duplicate reports?▼

The best way to prioritize GitHub issue triage is to assign confidence levels like High, Medium, or Low to potential duplicates. By evaluating primary and supporting evidence criteria, you can quickly identify high-confidence matches, link to the original issue, and suggest closure.

What are the limitations of automated duplicate bug tracking on GitHub?▼

A limitation of automated duplicate bug tracking is that analysis is restricted to a 90-day window of open and closed issues within a specific repository. Older reports or issues filed in different repositories are excluded from the semantic similarity and error pattern comparison.

Related Skills

Explore More Software Engineering Skills→
akiojinakiojin
83

gh-fix-issue

Analyze GitHub Issues and generate structured fix plans.

Community
Advanced
11547613341154761334

source-command-dedupe

Detects duplicate GitHub issues by querying issue summaries and filtering false positives.

Community
Intermediate
strawgatestrawgate

find-stale-issues

Identify stale, resolved, or duplicate GitHub issues via semantic similarity analysis.

Community
Advanced
warpdotdevwarpdotdev
820

github-issue-dedupe

Detect duplicate GitHub issues using keyword and semantic search.

Official
Intermediate