Menu
Repo-specific dedupe guidance . Only the categories declared overridable by the core dedupe-issue skill may be specialized here.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate a local static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate `.github/issue-triage/config.json` and `.github/CODEOWNERS`. Use when setting up triage automation on a new or existing repository for the first time.
Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.
Create a product spec from a GitHub issue in this repository by applying the local shared `write-product-spec` workflow with issue context and output paths. Use when an issue should be turned into a product spec artifact stored under `specs/issue-<issue-number>/product.md` and the agent should prepare file changes only, without creating commits or pull requests itself.
Create a technical spec from a GitHub issue in this repository by applying the local shared `write-tech-spec` workflow with issue context and output paths. Use when an issue should be turned into a tech spec artifact stored under `specs/issue-<issue-number>/tech.md` and the agent should prepare file changes only, without creating commits or pull requests itself.
Detect duplicate GitHub issues by comparing the incoming issue's title and description against issue candidates provided by the workflow.
| name | dedupe-issue-repo |
| specializes | dedupe-issue |
| description | Repo-specific dedupe guidance . Only the categories declared overridable by the core dedupe-issue skill may be specialized here. |
Use this skill when duplicate detection in this repository needs repository-local duplicate patterns or normalizations.
This file is a companion to the core dedupe-issue skill. It does not
redefine the duplicate-detection algorithm, the similarity thresholds,
or the output contract. It only specializes the override categories the
core skill marks as overridable.
.github/skills/dedupe-issue/SKILL.md.dedupe-issue workflow exactly.duplicate_of field in triage_result.json.The core dedupe-issue skill remains authoritative for the duplicate
detection procedure, similarity thresholds, ranking approach, 2-candidate
minimum before flagging an issue as a duplicate, output schema, and safety
rules.
This companion may only specialize:
This companion must not:
duplicate_of entry shape or add another reporting channelNo known-duplicate clusters have been captured for this repository yet.
The weekly update-dedupe loop will propose additions here over time
when maintainers repeatedly close issues as duplicates of the same
canonical thread.
The update-dedupe self-evolution flow may update this file with concise,
evidence-backed repository guidance. It must preserve the required wrapper
flow and boundaries above, and it must not update
.github/skills/dedupe-issue/SKILL.md or weaken the core duplicate-detection
contract.