What problem does it solve? Maintainers of busy repositories struggle to identify whether a new pull request or issue duplicates existing work, leading to fragmented discussions and wasted review effort. This Skill provides a structured triage workflow that gathers duplicate evidence, records maintainer judgments, and keeps one coherent duplicate group per problem. ## Core Features & Use Cases - Candidate Discovery: Uses gitcrawl for local history search, neighbor analysis, and cluster inspection, falling back to live GitHub search when local data is stale or missing. - Duplicate Grouping: Creates or reuses exactly one prtags group per duplicate cluster, with problem-centered titles and intent-based descriptions. - Judgment Persistence: Saves duplicate status, confidence, and rationale as prtags annotations, and lets prtags automatically sync the derived GitHub comment. - Use Case: A maintainer triaging PR #1234 can run this Skill to search for related threads, confirm the overlap with an earlier PR, group both items in prtags, and record a confirmed duplicate judgment with high confidence. ## Quick Start Use the tag-duplicate-prs-issues skill to decide whether PR #1234 in openclaw/openclaw is a duplicate and record the judgment in prtags.