tag-duplicate-prs-issues

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflows often require determining whether a pull request or issue is a duplicate, gathering evidence from multiple sources, and coordinating a single group that tracks the duplicate state and helps automate comment syncing.

Core Features & Use Cases

  • Evidence-driven triage: surface related PRs and issues using ghreplica and pr-search-cli
  • One-group-per-target discipline: create or reuse a single prtags group per duplicate cluster
  • State synchronization: save maintainer judgments in prtags and drive GitHub comment updates
  • Pre-reqs and setup: install companion skills and CLIs before starting

Quick Start

Start the workflow on a target PR or issue after installing ghreplica, prtags, and pr-search-cli.

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 identify and group duplicate PRs and issues for triage?

To identify and group duplicate PRs and issues, this Skill surfaces related targets using ghreplica and pr-search-cli, then clusters them into a single group. It enforces a one-group-per-target discipline to streamline maintainer triage workflows.

What is the best way to automate duplicate PR triage and sync GitHub comments?

Automating duplicate PR triage and comment syncing is achieved by persisting maintainer judgments in prtags, which then drives GitHub comment updates via authenticated API writes to synchronize the duplicate state across the grouped targets.

Do I need to install prtags and ghreplica before starting duplicate issue triage?

Yes, you need to install prtags, ghreplica, and pr-search-cli as prerequisites before starting. These companion CLIs collect the evidence, cluster the targets, and persist the judgments required for the duplicate triage workflow.

How does evidence-driven triage work for finding duplicate GitHub issues?

Evidence-driven triage works by gathering data from multiple sources through ghreplica and pr-search-cli to surface related PRs and issues. This collected evidence forms the basis for creating a single duplicate cluster per target.

Can I use this to group duplicate GitHub pull requests without manual searching?

You can group duplicate GitHub pull requests by relying on pr-search-cli and ghreplica to automatically surface related targets instead of manual searching. The Skill persists your final grouping decisions in prtags for state synchronization.