tag-duplicate-prs-issues

Cluster duplicate PRs and issues using gitcrawl and GitHub data.

5|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill tag-duplicate-prs-issues-p-sree-sai-pavan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/p-sree-sai-pavan/P.A.R.K.E.R/tree/main/gateway/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill tag-duplicate-prs-issues-p-sree-sai-pavan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

Core Features & Use Cases

  • Candidate discovery via gitcrawl for local history, context, and clusters.
  • Group related duplicates in prtags and save maintainer judgments for GitHub synchronization.
  • Maintain one coherent duplicate cluster per problem and ensure safe handling of tool availability and authentication.

Quick Start

Begin by running gitcrawl to identify candidate duplicates, verify them on GitHub, create or reuse a prtags group, and annotate the group state.

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

To find and group duplicate GitHub PRs and issues, this Skill uses gitcrawl to discover candidate duplicates from live data, clusters them into a single coherent group per problem in prtags, and syncs maintainer judgments back to GitHub with optional comments.

What is the best way to triage duplicate pull requests using gitcrawl?

Triage duplicate pull requests by running gitcrawl to identify local history and context clusters, verifying candidates on GitHub, then creating or reusing a prtags group to maintain one coherent duplicate cluster per problem.

Can I sync maintainer judgments about duplicate issues directly to GitHub?

Yes, you can sync maintainer judgments about duplicate issues directly to GitHub. The workflow persists grouping decisions from prtags to GitHub with optional comment synchronization to keep repository state updated.

Does grouping duplicate PRs require any specific tool state checks?

Grouping duplicate PRs requires proper tool-state checks before writes. The workflow enforces safe handling of tool availability and authentication to ensure secure persistence of duplicate group judgments to GitHub.

How do I maintain a single coherent cluster for related duplicate issues?

Maintain a single coherent cluster for related duplicate issues by using prtags to group related work, verifying candidates via live GitHub data, and annotating the group state to prevent fragmented duplicate tracking.

Why should I use prtags for duplicate PR triage instead of manual GitHub searches?

Use prtags for duplicate PR triage to automate candidate discovery via gitcrawl and persist maintainer judgments safely. It maintains one coherent group per problem, avoiding the fragmentation and missed context common in manual GitHub searches.