القائمة
Triage a GitHub issue by classifying severity, labelling waste category, proposing next action, and drafting a structured response
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Health check procedures D1–D14 for the Audit agent — structural validation, attention budget, version checks, workspace integrity, and static audit
Configure and manage Model Context Protocol servers for external tool access
Review a UI for accessibility — WCAG 2.1 AA compliance, semantic HTML, ARIA usage, keyboard navigation, focus management, colour contrast, and screen reader compatibility
Design or review a REST or GraphQL API — resource modeling, versioning strategy, error contract, OpenAPI/schema-first workflow, and security baseline
Generate a CHANGELOG.md entry from staged changes, a commit range, or a PR diff — following Keep a Changelog format with conventional commit classification
Set up and audit environment variable management — create .env.example, add startup validation, separate secrets from config, and document every variable
| name | issue-triage |
| description | Triage a GitHub issue by classifying severity, labelling waste category, proposing next action, and drafting a structured response |
| compatibility | >=1.4 |
Skill metadata: version "1.1"; license MIT; tags [triage, issues, github, lean, kaizen, bug, feature-request]; compatibility ">=1.4"; recommended tools [codebase, githubRepo, runCommands].
Systematically triage a GitHub issue using Lean waste categories, severity classification, and structured output.
Read the issue — Fetch the issue body, title, and all comments. Note the reporter, date, and any linked PRs or commits.
Reproduce context — Search the codebase for the affected file(s), function(s), or API mentioned in the issue. Read relevant code to confirm or deny the described behaviour.
Classify severity using these definitions:
critical — data loss, security vulnerability, crash in production path, or regression blocking releasemajor — significant functionality broken; workaround exists but is painfulminor — cosmetic, edge-case, or low-frequency impactadvisory — enhancement or improvement with no current breakageMap to waste category (§6 Muda — use the full catalogue; most common for issues):
| Waste code | Name | Typical issue signal |
|---|---|---|
| W1 Overproduction | Duplicate feature/issue already in backlog | "This was reported in #NNN" |
| W2 Waiting | Blocked on external dependency, PR, or decision | "Waiting on upstream fix" |
| W5 Inventory | Stale issue; may no longer be reproducible | Reported > 6 months ago, no recent activity |
| W6 Motion | Poor UX causing user confusion — not a code defect | "I couldn't find the button" |
| W7 Defects | Code correctness bug | Crash, wrong output, data loss |
| W8 Unused talent | Missing automation or documentation causing repeated effort | "We keep getting this question" |
Codes W3, W4, W9–W16 may apply — consult §6 for the full definitions if the above don't fit.
Propose next action — choose one:
fix — assign to a sprint, link to affected file(s)investigate — needs more information; list specific questions for the reporterclose-duplicate — link to the canonical issueclose-wontfix — explain the design decisionclose-stale — the issue is no longer reproducible or relevantdefer — valid but low priority; move to backlogDraft a comment — Write a structured GitHub comment using this template:
**Triage result**
| Field | Value |
|-------|-------|
| Severity | [critical / major / minor / advisory] |
| Waste category | [Wn — name] |
| Reproducible | [yes / no / unknown — explain] |
| Next action | [fix / investigate / close-duplicate / close-wontfix / close-stale / defer] |
**Summary**: [one sentence describing the issue and its impact]
**Recommended labels**: `[label1]`, `[label2]`
[If next action is investigate]:
> To help us investigate, please provide: [specific questions]
Verify — Confirm: