source-command-dedupe

Find likely duplicate GitHub issues and post a structured comment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you identify likely duplicate GitHub issues so maintainers can consolidate reports and reduce noise.

Core Features & Use Cases

  • Closed/irrelevant issue guardrails: checks whether the target issue is closed, doesn’t need deduping, or already has an earlier duplicates comment from the same maintainer.
  • Parallel duplicate search: summarizes the original issue and searches for duplicates using multiple parallel keyword strategies.
  • False-positive filtering: uses a secondary pass to filter out results that are not truly duplicates, then comments with up to three likely matches.

Quick Start

Use the source-command-dedupe skill when you want to dedupe a migrated source command dedupe by finding and commenting on up to three likely duplicate issues for a specific 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 deduplicate GitHub issues, this skill uses the GitHub CLI to summarize the target issue and run parallel keyword searches. It applies a secondary false-positive filtering pass before commenting with up to three likely matches.

What is the best way to cross-reference GitHub issue content for duplicates after migration?

Cross-referencing migrated GitHub issues requires parsing the target issue content and executing parallel keyword searches. This deduplication workflow ignores closed issues and filters out false positives to provide accurate duplicate detection.

Can I use GitHub CLI to detect and comment on duplicate bug reports?

Yes, GitHub CLI supports duplicate detection by executing parallel searches with a summary-driven query strategy. After filtering false positives, it comments directly on the issue with up to three likely duplicate matches.

Does GitHub issue deduplication work on closed issues or issues with existing duplicate comments?

No, the deduplication workflow includes guardrails that skip closed issues, irrelevant issues, and targets that already have an earlier duplicates comment from the same maintainer. This prevents redundant processing and unnecessary notifications.

How many likely duplicate issues can be identified and commented on in a single search?

The deduplication workflow identifies and comments on up to three likely duplicate GitHub issues per target. It applies false-positive filtering during a secondary pass to ensure the matches posted in the structured comment are accurate.