Menu
Repo-specific triage guidance. Only the categories declared overridable by the core triage-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.
Repo-specific dedupe guidance . Only the categories declared overridable by the core dedupe-issue skill may be specialized here.
| name | triage-issue-repo |
| specializes | triage-issue |
| description | Repo-specific triage guidance. Only the categories declared overridable by the core triage-issue skill may be specialized here. |
This file is a companion to the core triage-issue skill. It does not
redefine the triage output schema, safety rules, or follow-up-question
contract. It only specializes the override categories the core skill
marks as overridable.
ready-to-spec during triage. Maintainers repeatedly added this lifecycle label on issues #251, #239, and #134 after initial triage.ready-to-implement as a later lifecycle label, not a default initial-triage label. Only include it during triage when the issue already has an approved or clearly complete spec/plan, or the maintainer-provided issue context explicitly says implementation is approved. Maintainers added it after spec-readiness signals on issues #239 and #134.The label taxonomy for this repository is managed in .github/issue-triage/config.json. Prefer labels from that configuration, and avoid inventing new labels unless the prompt explicitly allows it.
No repo-specific follow-up patterns have been captured for this repository yet. Future updates may add concise, evidence-backed patterns when maintainer overrides reveal recurring follow-up needs that are actually specific to this repository.
The update-triage workflow may propose concise updates to this companion skill
when repeated maintainer correction signals across independent issues reveal
stable repo-specific triage guidance. Those updates must stay within the
override categories allowed by the core triage-issue skill and cannot change
the core triage contract, output schema, reserved label rules, safety rules, or
duplicate/follow-up exclusivity.