tag-duplicate-prs-issues

Identify and classify duplicate PRs and issues using ghreplica, pr-search-cli, and prtags.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zhcndoc/openclaw --skill tag-duplicate-prs-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-duplicate-prs-issues
Source: https://github.com/zhcndoc/openclaw/tree/main/.agents/skills/tag-duplicate-prs-issues
Command: npx skills add https://github.com/zhcndoc/openclaw --skill tag-duplicate-prs-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and classify duplicate PRs and issues within OpenClaw.

Core Features & Use Cases

  • Detects potential duplicates across PRs and issues
  • Creates or reuses a prtags group to store judgments and progress
  • Provides a guided workflow using ghreplica, pr-search-cli, and prtags for evidence gathering and decision making
  • Supports saving maintainer judgments and syncing with GitHub comments when configured

Quick Start

Start by selecting a target PR or issue and run this skill to gather duplicate evidence with ghreplica and pr-search-cli, then attach the result to a prtags group.

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 reads related items, forms duplicate clusters, and organizes them into a single group per problem to guide maintainer triage.

What is the best way to triage duplicate GitHub issues across a repository?

The best way to triage duplicate GitHub issues is using a guided workflow that gathers evidence from related PRs and issues, classifies duplicates, and stores maintainer judgments within a reusable group.

How do I automatically cluster similar GitHub pull requests during triage?

You can automatically cluster similar GitHub pull requests by running a skill that detects potential duplicates across PRs and issues, forms clusters, and attaches the results to a group for tracking.

Can I save maintainer judgments when grouping duplicate issues?

Yes, you can save maintainer judgments when grouping duplicate issues. The skill creates or reuses a group to store your decisions and progress, and can sync these judgments with GitHub comments when configured.

Does this duplicate issue detection work with both pull requests and issues?

Yes, duplicate issue detection works with both pull requests and issues. It operates across maintainer workflows by reading related PRs and issues together to identify and classify duplicates comprehensively.