菜单
Repo-specific triage guidance. Only the categories declared overridable by the core triage-issue skill may be specialized here.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate `.gitlab/issue-triage/config.json` and `.gitlab/CODEOWNERS`. Use when setting up triage automation on a new or existing repository for the first time.
Compare a merge request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during MR review when approved or repository spec context is available.
Create or update a GitLab merge request from a pushed branch after local review, base-branch sync, validation, and issue linking.
Create a product spec from a GitLab 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 merge requests itself.
Create a technical spec from a GitLab 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 merge 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.
The label taxonomy for this repository is managed in .gitlab/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.
