tag-duplicate-prs-issues

Detect duplicate GitHub PRs and issues, group them in prtags, and sync duplicate state.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill tag-duplicate-prs-issues-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill tag-duplicate-prs-issues-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about tag-duplicate-prs-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a GitHub PR is a duplicate of existing work?

Read the target PR with gh pr view, then search for candidates using gitcrawl threads, neighbors, and hybrid search. Verify each candidate against live GitHub data and confirm duplicates only when the problem, intent, and implementation context substantially overlap.

What evidence is needed before marking an issue as a duplicate?

Gather evidence from at least two categories, such as the same user-visible problem, same reproduction story, same fix area, or overlapping linked PRs. Title or keyword similarity alone is never sufficient to declare a duplicate.

What tools are required to run this duplicate triage workflow?

You need gitcrawl for local candidate discovery, the GitHub CLI (gh) for live state, and prtags installed and authenticated via OAuth device flow. Read-only discovery works without prtags, but writes require it.

Can a PR belong to multiple duplicate groups in prtags?

No. Duplicate groups are exclusive, so a PR or issue belongs to at most one group at a time. If a target appears to intersect two existing groups, stop and escalate to the maintainer instead of creating a second group.

When should I use live GitHub search instead of gitcrawl?

Use live gh search when the target is too new for the local store, when comments or reviews are missing locally, or when gitcrawl errors or lacks needed data. Always note when and why you fell back to live search.