What problem does it solve?
Maintainers waste significant time manually identifying duplicate pull requests and issues in GitHub repositories, leading to inconsistent grouping, repeated work on the same underlying problem, and unclear resolution tracking for related contributions.
Core Features & Use Cases
- Local candidate discovery: Uses gitcrawl to search local repository history for related PRs, issues, and closed threads as initial duplicate candidates.
- Live state verification: Uses the GitHub CLI to confirm current PR/issue state, comments, and code overlap to validate duplicate claims.
- Coherent group management: Creates or reuses problem-focused prtags groups to avoid fragmented duplicate clusters, following a strict one-group-per-problem rule.
- Structured judgment saving: Records maintainer duplicate decisions with confidence levels and rationales, and syncs group status to GitHub comments automatically.
- Use case: A maintainer can use this skill to quickly identify that 3 open PRs fixing the same gateway startup regression are duplicates, group them under a single problem-focused tag, and mark lower-priority ones as confirmed duplicates without manual comment writing.
Quick Start
Use the tag-duplicate-prs-issues skill to evaluate if the target GitHub pull request or issue is a duplicate of existing work, group related items, and save the triage judgment.