tag-duplicate-prs-issues

Group duplicate GitHub pull requests and issues into prtags groups.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill tag-duplicate-prs-issues-brikkoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill tag-duplicate-prs-issues-brikkoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers waste significant time manually identifying duplicate pull requests and issues in GitHub repositories, leading to inconsistent grouping, repeated work on the same underlying problem, and unclear resolution tracking for related contributions.

Core Features & Use Cases

  • Local candidate discovery: Uses gitcrawl to search local repository history for related PRs, issues, and closed threads as initial duplicate candidates.
  • Live state verification: Uses the GitHub CLI to confirm current PR/issue state, comments, and code overlap to validate duplicate claims.
  • Coherent group management: Creates or reuses problem-focused prtags groups to avoid fragmented duplicate clusters, following a strict one-group-per-problem rule.
  • Structured judgment saving: Records maintainer duplicate decisions with confidence levels and rationales, and syncs group status to GitHub comments automatically.
  • Use case: A maintainer can use this skill to quickly identify that 3 open PRs fixing the same gateway startup regression are duplicates, group them under a single problem-focused tag, and mark lower-priority ones as confirmed duplicates without manual comment writing.

Quick Start

Use the tag-duplicate-prs-issues skill to evaluate if the target GitHub pull request or issue is a duplicate of existing work, group related items, and save the triage 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 automatically group duplicate GitHub pull requests and issues?

You can automate grouping duplicate GitHub pull requests and issues by using gitcrawl to discover local repository history candidates and the GitHub API to verify live PR state, consolidating them into coherent problem-focused tags.

What is the best way to triage duplicate PRs in a software repository?

Triage duplicate PRs effectively by searching local git history for initial candidates, validating live state and code overlap via GitHub API, and saving structured maintainer judgments with confidence levels to sync group status automatically.

Does this duplicate issue grouping workflow require the prtags curation tool?

Yes, integrating with the prtags curation tool is required to create problem-focused duplicate groups, enforce a one-group-per-problem rule, save maintainer judgments, and automatically sync group status to GitHub comments.

Can I identify duplicate issues across both open and closed GitHub threads?

Yes, you can identify duplicate issues across open and closed threads because the skill leverages local git history via gitcrawl to search for related PRs, issues, and closed threads as initial duplicate candidates for maintainer triage.

Why does duplicate PR triage require checking local git history and live GitHub API data?

Checking local git history and live GitHub API data is necessary to discover initial duplicate candidates from past threads and validate current PR state, comments, and code overlap to ensure accurate duplicate identification.