triage-issue-reports
Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for automated or manual first-pass issue validation and routing.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 22
- Forks
- 1
01 前言 Front Matter
- name
- triage-issue-reports
- description
- Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for automated or manual first-pass issue validation and routing.
03 SKILL.md 正文
Triage issue reports
- Normalize the report into product area, environment, steps, expected behavior, observed behavior, frequency, and supplied evidence.
- Search for duplicates and known limitations when issue/search capabilities exist.
- Inspect the relevant code/feature map enough to judge plausibility without making edits.
- Classify as confirmed-enough-to-reproduce, needs-reporter-information, duplicate, expected behavior, or currently untriageable.
- Reply in the source thread/ticket when available with concise rationale and the next action. Do not invent a reproduction.
04 同仓库更多 Skills
why
Recover why a system or decision exists by triangulating source history and connected evidence. Use for rationale archaeology and historical questions.
unslop
Cut AI tells, filler prose, superficial -ing phrases, and bloated commentary from writing and code. Use for all written deliverables and code cleanup.
typescript-best-practices
Apply disciplined TypeScript modeling and boundary parsing. Use when reading or editing TypeScript.
technical-writing
Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Use for durable engineering prose.
teach
Teach a subsystem or change so the reader can reason about it, combining how and why evidence. Use for real understanding rather than summary.
tdd
Write a minimal failing test before implementation, make it pass with the simplest code, and refactor cleanly. Use when implementing bug fixes or features with clear verification targets.