
Github Issue Dedupe
- 138 installs
- 818 repo stars
- Updated May 12, 2026
- warpdotdev/oz-skills
Use github-issue-dedupe for development tasks
About
github-issue-dedupe: A skill skill for development. This skill provides functionality for development workflows.
- github-issue-dedupe
Github Issue Dedupe by the numbers
- 138 all-time installs (skills.sh)
- +1 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #2,664 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/warpdotdev/oz-skills --skill github-issue-dedupeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 138 |
|---|---|
| repo stars | ★ 818 |
| Last updated | May 12, 2026 |
| Repository | warpdotdev/oz-skills ↗ |
What it does
Use github-issue-dedupe for development tasks
Files
GitHub Duplicate Issue Detection
Find duplicate GitHub issues using multi-strategy search. Can be run manually or automated via GitHub Actions.
Workflow
1. Gather Issue Context
Extract key information from the target issue:
- Issue number and title
- Full body content
- Error messages or stack traces
- Keywords and technical terms
- Symptoms or behavior descriptions
2. Search Strategy
Use `gh` to search for related issues using multiple strategies:
- Keyword search from title and body
- Search for similar error messages
- Look for similar symptoms
3. Candidate Inspection
For each potential duplicate:
- View full issue with
gh issue view <number> - Compare:
- Root cause (same underlying problem?)
- Symptoms (identical behavior?)
- Error messages (exact match or very similar?)
- Affected components (same area of code?)
High confidence indicators:
- Identical error messages
- Same reproduction steps
- Same root cause with different descriptions
- One issue references the other
Low confidence (not duplicates):
- Similar symptoms but different causes
- Related but independent bugs
- Same component but different behaviors
4. Report Findings
If duplicates found:
Post comment on target issue:
gh issue comment <number> --body "This is potentially a duplicate of #123 and #456."Format rules:
- Single duplicate: "This is potentially a duplicate of #123."
- Two duplicates: "This is potentially a duplicate of #123 and #456."
- Three+ duplicates: "This is potentially a duplicate of #123, #456, and #789."
Only comment if high confidence (90%+ certain). When uncertain, do nothing.
Examples
Example 1: Clear Duplicate
Target Issue #150:
Title: "Dropdown menu stays open on mobile Safari"
Body: Clicking menu items doesn't close dropdown on iOSSearch process:
gh issue list --search "dropdown mobile safari"
gh issue list --search "menu doesn't close"
gh issue view 87 # Found similar issueIssue #87:
Title: "Mobile menu not closing after selection"
Body: On iOS Safari, menu stays open after clicking itemsDetermination: Duplicate
- Same symptom (menu stays open)
- Same platform (iOS Safari)
- Same root cause
Example 2: Similar But Not Duplicate
Target Issue #200:
Title: "Form validation error on submit"
Error: "Cannot read property 'value' of null"Search process:
gh issue list --search "form validation"
gh issue list --search "Cannot read property value null"
gh issue view 175Issue #175:
Title: "Form submission fails"
Error: "Cannot read property 'email' of undefined"Determination: Not duplicate
- Different error messages
- Different null references (value vs email)
- Related area but different bugs
Example 3: Multiple Duplicates
Target Issue #300:
Title: "Build fails with 'module not found' error"
Error: Error: Cannot find module './config'Search results:
- Issue #250: Same error, same module
- Issue #280: Same error, same module
- Issue #290: Different module error (not duplicate)
Action:
gh issue comment 300 --body "This is potentially a duplicate of #250 and #280."GitHub Duplicate Issue Detection
Automatically detect and flag duplicate GitHub issues using agent-based semantic search.
GitHub Actions Integration
Create .github/workflows/duplicate-check.yml:
name: Check for duplicate issues
on:
issues:
types:
- opened
jobs:
dedupe_check:
runs-on: ubuntu-latest
permissions:
contents: read
issues: write
steps:
- uses: actions/checkout@v4
- name: Run duplicate detection agent
uses: warpdotdev/warp-agent-action@v1
with:
warp_api_key: ${{ secrets.WARP_API_KEY }}
profile: ${{ vars.WARP_AGENT_PROFILE || '' }}
environment_id: ${{ vars.WARP_AGENT_ENVIRONMENT }}
skill_spec: "warpdotdev/oz-skills:github-issue-dedupe"
prompt: |
Find duplicates of issue #${{ github.event.issue.number }} in ${{ github.repository }}.
Export GH_TOKEN first:export GH_TOKEN=${{ secrets.GITHUB_TOKEN }}
Current Issue:
- Number: #${{ github.event.issue.number }}
- Title: ${{ github.event.issue.title }}
- Body: ${{ github.event.issue.body }}Setup
1. Add WARP_API_KEY to repository secrets 2. (Optional) Set WARP_AGENT_PROFILE variable for custom agent config 3. Workflow triggers automatically on new issues 4. Agent comments on duplicates found
The skill_spec parameter loads this skill's workflow and best practices automatically.