source-command-dedupe

To find duplicate GitHub issues during triage, this Skill validates issue status, checks existing duplicates, summarizes content, and orchestrates parallel keyword searches to return up to three likely references.

The best way to consolidate similar GitHub reports is orchestrating parallel search agents with varied keywords to surface up to three likely duplicates, then commenting with detected references for review.

Yes, you can use the gh CLI to detect duplicate issues in migration scenarios by orchestrating a multi-step workflow that evaluates issue status and runs parallel searches for consolidation.

Parallel search agent orchestration for duplicate detection spawns multiple agents with varied keywords extracted from an issue summary, surfacing up to three potential matches for final comment posting.

Yes, the duplicate issue detection workflow checks whether an issue already has existing duplicates before spawning parallel search agents, preventing redundant searches on previously triaged reports.

A limitation is that results are capped at three likely duplicate references, and detection relies on keyword-based parallel searches and issue summaries rather than semantic analysis of entire conversation threads.