tag-duplicate-prs-issues

Determine duplicate Kova pull requests or issues and record judgments in prtags.

Updated Aug 27, 2026

Search Tags:#github #pull requests #issues #prtags #maintainer workflow #duplicate triage #evidence-based grouping

Ready to run

npx skills add https://github.com/chiragborse1/KovaLab --skill tag-duplicate-prs-issues-chiragborse1

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers determine whether a pull request or issue is a duplicate of existing work, then organizes the related items into a coherent prtags duplicate cluster.

Core Features & Use Cases

Duplicate triage with evidence: Reads the target and gathers support using GitHub mirroring and similarity search across PRs/issues.
One-cluster enforcement: Prevents ambiguous or conflicting duplicate grouping by applying a strict one-group rule per target.
prtags-backed curation and sync: Writes maintainer judgment into prtags (status, confidence, rationale) so prtags can own the GitHub comment projection.

Use this when you are doing maintainer triage and need to close/retag duplicates safely without relying only on title similarity.

Quick Start

Ask the agent to run tag-duplicate-prs-issues to judge whether PR or issue #<n> is a duplicate, then create or reuse the right prtags group and write the maintainer decision.

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 automatically detect and tag duplicate GitHub pull requests or issues?▼

To automatically detect and tag duplicate GitHub pull requests or issues, this Skill gathers evidence using GitHub mirroring and similarity search, then records the judgment into prtags by creating or reusing a duplicate cluster.

What is the best way to group duplicate GitHub issues during maintainer triage?▼

Grouping duplicate GitHub issues during maintainer triage is best handled by applying a strict one-cluster rule per target, ensuring evidence-based grouping without ambiguous or conflicting duplicate assignments.

How does evidence-based duplicate triage work for pull requests?▼

Evidence-based duplicate triage for pull requests works by reading the target item and gathering support across related PRs and issues using external CLI tools, ranking candidates before writing a final decision.

Do I need prtags and external CLI tools to manage duplicate PR clusters?▼

Yes, managing duplicate PR clusters requires prtags for group creation and idempotent field writes, alongside ghreplica/ghr for read-path evidence and pr-search-cli for candidate similarity hints.

Why does this duplicate triage workflow enforce a one-cluster rule per issue?▼

The duplicate triage workflow enforces a one-cluster rule per issue to prevent ambiguous grouping, ensuring a single target cannot be assigned to conflicting duplicate groups simultaneously.