tag-duplicate-prs-issues

Identify duplicate PRs and issues using ghreplica and pr-search-cli evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rigeoben/fairy --skill tag-duplicate-prs-issues-rigeoben
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/rigeoben/fairy/tree/main/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/rigeoben/fairy --skill tag-duplicate-prs-issues-rigeoben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Search for duplicate PRs and issues, group related work in prtags, and keep GitHub in sync with maintainer judgments.

Core Features & Use Cases

  • Identify duplicate PRs and issues across the repository using evidence collection from ghreplica and pr-search-cli.
  • Group related items in a single prtags group to maintain a coherent perspective and avoid multiple competing verdicts.
  • Save maintainer judgments in prtags to drive subsequent GitHub comment synchronization and status tracking.

Quick Start

Install the companion skills and CLIs (ghreplica, prtags, and pr-search) and then run the tagging workflow to classify a target PR or issue as duplicate or not.

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 find and tag duplicate GitHub PRs and issues?▼

You find and tag duplicate GitHub PRs and issues by analyzing text, code, and context to surface similarity evidence. The workflow clusters related items and records maintainer judgments in a prtags group.

What is the best way to group duplicate PRs for repository maintenance?▼

The best way to group duplicate PRs is clustering similar items into a single prtags group. This maintains a coherent perspective and avoids competing verdicts during repository maintenance workflows.

Do I need ghreplica and pr-search-cli to identify duplicate issues?▼

Yes, identifying duplicate issues requires ghreplica and pr-search-cli for evidence gathering. The workflow enforces these tools to analyze repository context and group related issues accurately.

How does prtags sync maintainer judgments with GitHub?▼

prtags syncs maintainer judgments with GitHub by saving duplicate classifications to drive subsequent comment synchronization and status tracking. It records maintained verdicts for grouped PRs and issues.

Can I classify GitHub issues as duplicates without authenticated access?▼

No, classifying GitHub issues as duplicates requires authenticated access. The duplicate tagging workflow enforces setup steps and authenticated access to gather evidence and update prtags.

When should I avoid using automated duplicate PR detection?▼

You should avoid automated duplicate PR detection when lacking authenticated repository access or missing companion CLI setups. The workflow strictly requires ghreplica, prtags, and pr-search to function correctly.