Menu
Deep-triage a GitHub issue — classify, analyze against the code, draft an answer, and apply the disposition
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | triage-issue |
| description | Deep-triage a GitHub issue — classify, analyze against the code, draft an answer, and apply the disposition |
| argument-hint | #123 (a single issue) | empty (sweep all needs-triage) | --help |
Do the heavy lifting of triaging a user-filed issue on log2n-io/Typhon: classify it, analyze it against the
actual code/docs/rules, decide a disposition, draft an answer, and — after you confirm — apply labels, Issue
Type, Area/Product, project placement, and post the reply.
This is the local, code-aware counterpart to the automated first-pass .github/workflows/issue-triage.yml
(which only adds rough labels + a comment). This skill has the whole repo in context and your org-level
credentials, so it does what the CI bot deliberately cannot.
Companion skill:
/create-issue— reuse its Field Reference (project ID, Status/field IDs, sub-issue linking) and_helpers.mdpatterns. Taxonomy is identical: Issue TypesTask/Bug/Feature/Question/Epic; labelsbug, enhancement, documentation, performance, refactoring, testing, technical-debt; issue-level fields Area / Product; Milestone = release maturity; Epic→Feature→Task hierarchy.
$ARGUMENTS
If $ARGUMENTS contains --help or -h, print this and stop:
/triage-issue [#N]
Deep-triage a GitHub issue (or sweep all needs-triage issues).
Arguments:
#N Issue number to triage. If omitted, sweep every OPEN issue labelled `needs-triage`.
--help, -h Show this help
What it does (per issue):
1. Fetches the issue and reads referenced code / docs / rules / tests
2. Classifies: Issue Type, Area, Product, severity, labels
3. Analyzes: reproduces the claim against the code (file:line), checks dups + QUARANTINE.md
4. Verdict: real bug / duplicate / misunderstanding / needs-info / works-as-designed
5. Drafts a reply + a recommended disposition
6. Asks you to confirm, then applies labels/type/fields + posts the comment
mcp__GitHub__get_issue (owner log2n-io, repo Typhon, the number). Capture title, body, author,
existing labels, current Issue Type, and the number/id. For a sweep, first
mcp__GitHub__search_issues repo:Log2n-io/Typhon is:issue is:open label:needs-triage.
file:line), the relevant claude/ design docs and
claude/rules/ invariants, and any related tests. Docs are the source of truth — read them before
reasoning (see root CLAUDE.md).test/Typhon.Engine.Tests/QUARANTINE.md and existing issues for known / duplicate reports.CLAUDE.md) and cite concrete evidence.Bug / Feature / Question / Task / Epic.Engine / Workbench.bug, enhancement, documentation, performance, refactoring, testing, technical-debt, needs-info.One of: real bug (repro confirmed) · duplicate (link the original) · misunderstanding
(explain the correct usage) · needs-info (list exactly what's missing) · works-as-designed (cite
the rule/design) · valid feature/question. State a confidence and the file:line / doc evidence.
Feature/Task via /create-issue; close as
duplicate/answered/not-planned; or leave open with needs-info.Present the classification + verdict + drafted reply and confirm via AskUserQuestion before any write.
On approval, apply with gh (your local creds have org permissions — no PROJECT_TOKEN needed):
# Labels
gh issue edit <n> --repo log2n-io/Typhon --add-label "<l1>,<l2>" --remove-label needs-triage
# Issue Type (primary classifier)
gh issue edit <n> --repo log2n-io/Typhon --type "Bug" # or Feature / Question / Task / Epic
# Milestone (release maturity, if applicable)
gh issue edit <n> --repo log2n-io/Typhon --milestone "alpha-1"
# Comment (post the drafted reply)
gh issue comment <n> --repo log2n-io/Typhon --body "<reply>"
/create-issue
Step 6); mirror the parent Epic if linked.gh project item-add 1 --owner Log2n-io --url <url> then Status (see /create-issue
Steps 4–5 for the item-id + field IDs).gh issue close <n> --repo log2n-io/Typhon --reason "not planned" (or completed), after
the explaining comment./create-issue to open the Feature/Task and link it.AskUserQuestion confirmation. This skill proposes; you approve.file:line / doc evidenceRun regression benchmarks, track results, and generate trend reports
Complete a sub-issue of an umbrella issue - close it, check parent checkbox, update design doc
Complete work on a GitHub issue - close issue, update artifacts, prompt for doc updates
Run code coverage analysis, track class-level results, and generate trend reports
Create a GitHub issue and add it to the Typhon org project
Implement a GitHub issue end-to-end — scope it (whole issue or specific phases), build an acceptance-criteria plan from its design doc, get the plan approved, then develop autonomously with tests and a mandatory code review.