Help us improve
Share bugs, ideas, or general feedback.
From frontend-skills
Triage issues through a state machine of triage roles for GitHub and Jira trackers. Handles bug investigation, filing tickets with TDD fix plans, and issue workflow management.
npx claudepluginhub redpanda-data/ui-harness --plugin frontend-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-skills:triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Move issues on tracker through small state machine of triage roles.
Triage issues through a state machine (bug/enhancement, needs-triage/needs-info/ready-for-agent/ready-for-human/wontfix). Query, label, and transition issues on the project tracker.
Triages issues through a state machine with category and state roles. Helps manage bug reports, feature requests, and prepare issues for AFK agents.
Triages project issues through a state machine with category and state roles. Use when creating issues, reviewing bugs/feature requests, preparing issues for AFK agents, or managing issue workflow.
Share bugs, ideas, or general feedback.
Move issues on tracker through small state machine of triage roles.
When explore codebase, use project domain glossary so titles, comments, agent briefs match project language. Respect ADRs in area touched.
Every comment posted to tracker during triage must start with:
> *This was generated by AI during triage.*
Detect by git remote -v + repo conventions:
github.com remote) -> use gh.atlassian/ config) -> use acliBoth present (GitHub repo + Jira tickets) -> ask which user want file/triage against.
Two category roles:
bug -- something brokenenhancement -- new feature or improvementFive state roles:
needs-triage -- maintainer must evaluateneeds-info -- wait on reporter for more infoready-for-agent -- fully specified, ready for AFK agentready-for-human -- need human implementationwontfix -- will not actionEvery triaged issue carry exactly one category role + one state role. Conflicting states -> flag and ask before act.
Canonical role names. Actual label/status strings in tracker may differ -- when differ, infer from existing labels/statuses on project, ask once, remember within session.
ghacli.out-of-scope/ knowledge baseUser invoke /triage and describe want in natural language. Examples:
Interpret and act.
Query tracker. Present three buckets, oldest first:
needs-triage -- evaluation in progressneeds-info with reporter activity since last triage notes -- need re-evaluationShow counts + one-line summary per issue. Let maintainer pick.
Gather context. Read full issue (body, comments, labels/status, reporter, dates). Parse prior triage notes so resolved questions not re-asked. Explore codebase using project domain glossary, respect ADRs in area. Read .out-of-scope/*.md -- surface any prior rejection resembling issue.
Recommend. Tell maintainer category + state recommendation with reasoning, plus brief codebase summary relevant to issue. Wait for direction.
Reproduce (bugs only). Before grill, attempt repro: read reporter steps, trace code, run tests or commands. Report what happened -- successful repro with code path, failed repro, or insufficient detail (strong needs-info signal). Confirmed repro make much stronger agent brief. For root-cause investigation + TDD fix plan, see REFERENCE.md#tdd-fix-plan-mode.
Grill (if needed). Issue need flesh out -> run /grill-me for a fast grill or /grill-with-docs when domain language/ADRs matter.
Apply the outcome:
ready-for-agent -> post agent brief comment (AGENT-BRIEF.md)ready-for-human -> same structure, but note why can't delegateneeds-info -> post triage notes (see REFERENCE.md)wontfix (bug) -> polite explanation, then closewontfix (enhancement) -> write to .out-of-scope/, link from comment, then close (OUT-OF-SCOPE.md)needs-triage -> apply role; optional comment if partial progressUser say "move #42 to ready-for-agent" -> trust them, confirm what about to do (role changes, comment, close), then act. Skip grill. If move to ready-for-agent without grill session, ask whether want agent brief written.
Prior triage notes exist on issue -> read them, check whether reporter answered outstanding questions, present updated picture before continue. Don't re-ask resolved questions.
Full transition table: REFERENCE.md#state-machine.