skills.rest
warpdotdev
warpdotdevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dedupe-issue

Compare GitHub issue titles and descriptions to flag potential duplicates.

292|39|Updated Mar 17, 2026
Search Tags:#github#issues#triage#similarity#issue-management#deduplicate
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill dedupe-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dedupe-issue
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/dedupe-issue
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill dedupe-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deduplicate issues by comparing an incoming GitHub issue's title and description against the repository's existing issues to surface potential duplicates during triage.

Core Features & Use Cases

  • Compare new issues against open and recent closed issues to identify likely duplicates.
  • Normalize titles and descriptions to reduce false negatives and surface relevant matches.
  • Integrate into triage workflows to reduce duplication and speed up issue routing.

Quick Start

Compare the incoming issue against the repository's open issues to surface likely duplicates.

Frequently Asked Questions about dedupe-issue

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

FAQPage Schema
How do I identify duplicate GitHub issues during triage?▼

You can identify duplicate GitHub issues by comparing incoming issue data against existing repository issues. This skill fetches open and recent closed issues via the GitHub API, normalizes titles and descriptions, ignores pull requests, and flags potential duplicates for review.

How does issue deduplication handle closed issues and pull requests?▼

Issue deduplication compares against both open and recent closed issues while explicitly ignoring pull requests. It normalizes text data to reduce false negatives, ensuring only relevant issue matches are surfaced for triage review.

What is the best way to find similar issues in a large open-source repository?▼

The best way to find similar issues in a large open-source repository is to normalize incoming titles and descriptions, then compare them against existing open and recently closed issues. This surfaces two or more potential duplicates for reviewer attention.

Does this issue triage approach work for repositories with many open issues?▼

Yes, this issue triage approach is designed for open-source projects with many issues. It integrates into triage workflows to surface potential duplicates, reducing manual review overhead and speeding up issue routing.

Why does issue matching normalize titles and descriptions?▼

Issue matching normalizes titles and descriptions to reduce false negatives and surface relevant matches. This ensures minor formatting or wording variations do not prevent the identification of likely duplicate GitHub issues.

Related Skills

Explore More Software Engineering Skills→
cedanlcedanl

release-notes

Draft Dutch release notes from merged PRs and closed issues.

Official
Advanced
JsplixJsplix

ibank-worklog-duplicate-audit

Audits iBank worklog datasets for duplicate entries and generates review packets.

Community
Intermediate
C0ntr0lledCha0sC0ntr0lledCha0s
8

github-issues

Triage GitHub issues for Logseq Template Graph with validation and labeling.

Community
Intermediate
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic