tag-duplicate-prs-issues

Group duplicate GitHub pull requests and issues using gitcrawl and prtags.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/wangqianCAI/OBI --skill tag-duplicate-prs-issues-wangqiancai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/wangqianCAI/OBI/tree/main/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/wangqianCAI/OBI --skill tag-duplicate-prs-issues-wangqiancai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing fragmented issue trackers by identifying, grouping, and annotating duplicate pull requests and issues to maintain a clean and actionable project backlog.

Core Features & Use Cases

  • Intelligent Discovery: Leverages local history via gitcrawl to find related threads and potential duplicates before checking live GitHub data.
  • Maintainer Curation: Provides a structured workflow to create or reuse duplicate groups in prtags, ensuring each problem is tracked in one coherent cluster.
  • Use Case: When multiple users report the same bug or submit overlapping PRs, use this skill to consolidate them into a single duplicate group, saving maintainers from reviewing the same implementation context repeatedly.

Quick Start

Use the tag-duplicate-prs-issues skill to analyze the target issue or pull request and group it with any existing duplicates found in the repository.

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 group duplicate GitHub issues and pull requests automatically?

To group duplicate GitHub issues, this skill coordinates local gitcrawl history with live GitHub API data to identify duplicate clusters and apply standardized metadata for maintainer triage efficiency.

What is the best way to streamline GitHub triage for overlapping pull requests?

Streamlining GitHub triage involves consolidating overlapping pull requests into a single duplicate group using prtags, which saves maintainers from reviewing the same implementation context repeatedly.

Do I need the prtags CLI to manage duplicate issue tracking?

Yes, managing duplicate issue tracking requires integration with the prtags CLI to manage group state, annotations, and automated comment synchronization across the validated duplicate clusters.

How does gitcrawl history validate duplicate GitHub PR clusters?

Gitcrawl history validates duplicate GitHub PR clusters by locally finding related threads and potential duplicates before cross-referencing them with live GitHub API data to ensure accurate grouping.

Can I use this skill to annotate duplicate issues without manual maintainer curation?

No, maintainer curation is required to create or reuse duplicate groups in prtags, ensuring each problem is tracked in one coherent cluster rather than relying solely on automated annotation.

When should I avoid automated duplicate tracking for my repository backlog?

Avoid automated duplicate tracking if your repository lacks sufficient local gitcrawl history or live GitHub API access, as both are required to validate and group duplicate issues accurately.