source-command-dedupe

Identify and report potential duplicate GitHub issues via parallel searches.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/xkl2013/lobe --skill source-command-dedupe-xkl2013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-dedupe
Source: https://github.com/xkl2013/lobe/tree/main/.agents/skills/source-command-dedupe
Command: npx skills add https://github.com/xkl2013/lobe --skill source-command-dedupe-xkl2013

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of finding duplicate GitHub issues, saving time and reducing manual effort.

Core Features & Use Cases

  • Duplicate Detection: Scans for and identifies potential duplicate GitHub issues.
  • Automated Analysis: Utilizes multiple agents to search for duplicates using various keywords and search approaches.
  • Filtering: Filters out false positives to ensure accurate duplicate identification.
  • Reporting: Generates a list of up to three likely duplicates for review and comment on the original issue.
  • Use Case: When managing a large number of GitHub issues, this Skill helps streamline the process of identifying duplicates and maintaining issue integrity.

Quick Start

Run the source-command-dedupe skill to find and report duplicate issues for a given GitHub issue.

Frequently Asked Questions about source-command-dedupe

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

FAQPage Schema
How do I find duplicate GitHub issues automatically?

To find duplicate GitHub issues, this Skill uses multiple agents to run parallel searches with various keywords, filtering out false positives to generate a list of up to three likely duplicates for review.

How does parallel processing work for duplicate issue detection?

Parallel processing for duplicate detection works by deploying multiple agents that simultaneously search GitHub issues using different keywords and approaches, ensuring accurate identification while saving manual effort.

Do I need GitHub API access to detect duplicate issues?

Yes, GitHub API access is required to detect duplicate issues, as the Skill relies on it to scan repositories and retrieve issue data for parallel search and filtering.

What is the best way to manage a large number of GitHub issues?

The best way to manage a large number of GitHub issues is automating duplicate detection, which scans for potential overlaps and reports up to three likely duplicates to comment on the original issue.

Can I filter out false positives when identifying duplicate issues?

Yes, you can filter out false positives when identifying duplicate issues; the Skill applies filtering mechanisms after parallel searches to ensure accurate duplicate identification before reporting.

Why does duplicate issue detection report up to three matches?

Duplicate issue detection reports up to three matches to provide a concise list of likely duplicates for manual review, allowing you to verify accuracy and comment on the original issue without overwhelming the workflow.