tag-duplicate-prs-issues

Identify duplicate PRs and issues using gitcrawl and prtags groups.

7|12|Updated Mar 10, 2026

Search Tags:#automation #issues #pr #triage #duplicate #prtags #gitcrawl

Ready to run

npx skills add https://github.com/borealBytes/my-farm-advisor --skill tag-duplicate-prs-issues-borealbytes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill tag-duplicate-prs-issues-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and clusters duplicate PRs and issues to reduce triage time and ensure consistent handling across the project.

Core Features & Use Cases

Use gitcrawl to discover candidate duplicates locally and on GitHub.
Create or reuse a single prtags group to represent a duplicate cluster.
Record maintainer judgments and rationale using prtags annotations for downstream syncing.
Manage and synchronize group state with GitHub comments without manual posting.

Quick Start

Initiate the workflow by discovering duplicates with gitcrawl, then group them in prtags and apply maintainer judgments.

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 identify duplicate issues and pull requests for triage?▼

Automatically identify duplicate issues and PRs by using gitcrawl to compare titles, bodies, and related threads against current repository items, then clustering the matched targets into a single group for consistent handling.

What is the best way to group duplicate pull requests and issues together?▼

The best way to group duplicate PRs and issues is to organize related targets into one cluster, creating or attaching a target and recording maintainer judgments to persist the grouping decision for downstream automation.

How do I sync duplicate issue triage decisions with GitHub comments?▼

You can sync duplicate triage decisions with GitHub comments by persisting maintainer judgments in annotations, relying on the integrated workflow to automatically synchronize the group state without manual posting.

Can I use gitcrawl to discover duplicate issues locally and on GitHub?▼

Yes, you can use gitcrawl to discover candidate duplicate issues and PRs both locally and on GitHub, comparing their titles and bodies to find related threads before organizing them into groups.

Does this approach require manually posting comments to close duplicate PRs?▼

No, this approach does not require manually posting comments, because it relies on an integrated workflow that automatically syncs the recorded group state and maintainer judgments directly to GitHub comments.

How are maintainer judgments and rationale recorded for duplicate issue clusters?▼

Maintainer judgments and rationale are recorded using annotations within the duplicate cluster, ensuring the triage decisions are persisted for downstream syncing and consistent project management.