tag-duplicate-prs-issues

To identify duplicate GitHub PRs and issues, this skill examines user-visible problem statements and implementation context to detect related work. It gathers evidence using ghreplica and clusters candidates with pr-search-cli before grouping them.

The best way to group duplicate GitHub issues for triage is to create or reuse a single prtags group per duplicate story. This preserves a coherent narrative and records maintainer judgments directly in the group metadata.

When handling existing duplicate groups on GitHub, the workflow respects them and avoids creating multiple groups for the same target. It syncs maintainer decisions back to GitHub by persisting them in the existing prtags group metadata.

Yes, you can use prtags to record maintainer triage decisions for pull requests. The workflow persists maintainer curation judgments in prtags group metadata, surfacing a consolidated view for developers and reviewers.

Yes, you need pr-search-cli and ghreplica to triage duplicate PRs effectively. The workflow leverages ghreplica for evidence gathering and pr-search-cli for candidate clustering to accurately identify real duplicates among PRs and issues.