triage

Investigate tickets and post read-only findings back to the issue tracker.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill triage-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/triage
Command: npx skills add https://github.com/danielsuguimoto/skills --skill triage-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Answering ticket questions or debugging reported issues requires reading specs, tracing code, and querying databases before writing a response — a slow, error-prone manual process. This Skill automates that investigation and syncs structured findings back to the ticket without touching any code. ## Core Features & Use Cases - Mode Detection: Reads the full ticket thread and classifies it as an ask (question to answer) or debug (bug to root-cause) workflow. - Evidence Gathering: Uses code navigation, database inspection, and doc lookup to build file:line-cited findings, with ranked falsifiable hypotheses for debug mode. - Ticket Sync: Posts findings back to the issue tracker as a private technical note, restating any externally supplied question for traceability. - Use Case: A support ticket reports that invoice totals are wrong for one customer. The Skill loads the ticket, traces the calculation code path, verifies live database rows, ranks hypotheses, and posts a root-cause note with evidence — all read-only. ## Quick Start Triage the ticket at https://tracker.example.com/tickets/1234 and post your findings as a private note.

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a support ticket with an AI agent?▼

Provide the ticket URL and the Skill loads the full thread including comments and attachments, classifies it as a question or a bug, gathers evidence from code and databases, then syncs findings back to the ticket as a private note.

How to root-cause a bug reported in a ticket?▼

The debug mode derives expected versus actual behavior, generates 3-5 ranked falsifiable hypotheses, traces the code path from user action to failure, and verifies against the live database before stating the root cause with evidence.

Does ticket triage modify code or create commits?▼

No. The Skill is strictly read-only — it never modifies, creates, or deletes files and never runs git commit or push. It only reads code, queries databases, and posts findings to the ticket.

What happens when ticket investigation hits a blocker?▼

Blockers are escalated to the user in chat first, since most resolve with a quick answer. Only blockers needing input from other teams or customers are posted to the ticket, avoiding unnecessary round-trips.

Why are project docs required before triaging a ticket?▼

The Skill reads project-root spec files for code navigation, database tools, doc lookup, and issue trackers to know which tools to use. If a file is missing it falls back to native tools and notes the gap rather than inventing contents.