tag-duplicate-prs-issues

Use gitcrawl to search local repository history, neighbors, and clusters for candidates, then verify each candidate against live GitHub state with gh pr view or gh issue view. Confirm duplicates only when evidence from at least two categories matches, such as the same problem statement and overlapping changed files.

A duplicate decision requires evidence from at least two categories, such as the same problem statement, overlapping changed files, the same fix direction, or the same linked issue. Title or keyword similarity alone is never sufficient.

Read-only discovery with gitcrawl and gh works without prtags, but prtags must be installed and logged in via OAuth device flow before any group or annotation writes. If it is missing at the write step, the workflow stops and asks you to install or authenticate.

No. The one-group rule treats duplicate groups as exclusive, so a PR or issue belongs to at most one group. If a target appears to intersect two existing groups, the workflow stops and escalates to the maintainer instead of creating a second group.

Writes fail when the prtags mirror has not yet caught up with the target object on GitHub. The workflow keeps any successful group state, reports the missing target, and defers the target-level annotation rather than forcing a fallback write.