Agent skill · marketing growth · steipete

tag-duplicate-prs-issues

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

Why this skill is useful

Adds specific commands and workflows for using gitcrawl and prtags to manage duplicate PRs and issues effectively.

What it needs

Requires prtags installed locally. Requires github account access. About 9k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.

What this skill does

Tag Duplicate PRs and Issues Use this skill when a maintainer needs to decide whether a pull request or issue is a duplicate of existing work. This skill is for maintainer triage and grouping. It is not for reviewing the implementation quality of a PR. Required Setup Do not write duplicate groups or annotations until this setup is complete. Read-only discovery can still proceed with gitcrawl and live gh. Companion Skills Use $gitcrawl first for local candidate discovery. Use the prtags skill from the prtags repo at skills/prtags/SKILL.md when it is available. Install the CLIs Install prtags from the pinned release below. Do not rely on an old local build unless the maintainer explicitly wants to test unreleased behavior. prtags CLI install path: prtags lives outside the OpenClaw organization, so this install stays pinned to a reviewed version that the Go module proxy resolves and the public checksum database verifies. GOBIN keeps the installed executable in the same user-local directory as the previous installer, so an existing $HOME/.local/bin PATH continues to resolve the newly installed version. Do not install it by piping a remote script into a shell, and do not point the install at a branch: either one executes whatever that third party serves at run time, with the maintainer's own privileges. Moving to a newer prtags release is a reviewed change to this file, not a mid-task step. Authenticate prtags prtags should be logged in with the maintainer's own GitHub account through OAuth device flow. Do not use a shared maintainer token for interactive triage. The expected outcome is that prtags stores the logged-in maintainer identity locally and uses that account for authenticated writes. Missing-Setup Rule Do not require an up-front preflight before starting the workflow. Proceed with the normal steps until you actually need a tool or account state. As soon as you discover that prtags is missing or not logged in at the write step, stop immediately. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills steipete/tag-duplicate-prs-issues

View the source on GitHub

Browse the @skills marketplace