tag-duplicate-prs-issues

Name: tag-duplicate-prs-issues
Availability: InStock
Author: Frank

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

Updated Apr 24, 2026

Search Tags:#github #duplicate #prtags #ghreplica #pr-search-cli

Ready to run

npx skills add https://github.com/frankhli843/gemmahermes --skill tag-duplicate-prs-issues-frankhli843

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/frankhli843/gemmahermes/tree/main/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/frankhli843/gemmahermes --skill tag-duplicate-prs-issues-frankhli843

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers need a coherent workflow to determine if PRs and issues are duplicates, gather evidence from sources like ghreplica and pr-search-cli, group related items in prtags, and sync the grouping back to GitHub.

Core Features & Use Cases

Collect duplicate evidence from ghreplica and pr-search-cli to assess similarity between PRs and issues.
Create or reuse a single prtags group per duplicate cluster to avoid fragmentation.
Save maintainer judgments in prtags and drive GitHub comment synchronization for group-level visibility.

Quick Start

Start the duplicate triage by running ghreplica and pr-search-cli, then create or join a prtags group to record the judgment.

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 identify and group duplicate GitHub PRs and issues?▼

Identify duplicate GitHub PRs and issues by gathering similarity evidence with ghreplica and pr-search-cli, then group related items into a single prtags cluster to avoid fragmentation.

What is the best way to manage duplicate PR triage across a repository?▼

Managing duplicate PR triage involves collecting evidence from pr-search-cli, recording maintainer judgments in a dedicated prtags group, and synchronizing the outcome back to GitHub for group-level visibility.

Do I need to authenticate ghreplica and prtags before triaging duplicate issues?▼

Yes, ghreplica, pr-search-cli, and prtags must all be available and authenticated before you can gather evidence, save maintainer judgments, and synchronize duplicate groupings back to GitHub.

Can I sync maintainer duplicate judgments back to GitHub comments?▼

Yes, maintainer judgments saved in prtags drive GitHub comment synchronization, ensuring that group-level visibility and duplicate outcomes are updated directly on the original PRs and issues.

Why should I use a single prtags group for duplicate PR clusters?▼

Using a single prtags group per duplicate cluster avoids fragmentation, consolidating related PRs and issues together while preserving the maintainer judgment for future reference.

What does ghreplica do in the duplicate issue detection workflow?▼

In the duplicate detection workflow, ghreplica collects similarity evidence across related PRs and issues, providing the foundational data needed to assess whether items are actual duplicates before grouping them.