skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

issue-triage

Fetch GitHub issues via gh, classify them, and identify code areas.

37|2|Updated Jun 28, 2025
Search Tags:#investigation#github#handoff#root-cause#bug#issue-triage#jellyrock
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill issue-triage-jellyrock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/issue-triage
Command: npx skills add https://github.com/jellyrock/jellyrock --skill issue-triage-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issues often sit untriaged, misclassified, or lack the context developers need to act on them efficiently, causing delays and wasted investigation time.

Core Features & Use Cases

  • End-to-End Triage: Fetches issue data via gh, classifies bugs/features/enhancements, and identifies probable code areas in the JellyRock codebase.
  • Investigation Handoffs: Writes durable handoff packets to the .claude/handoffs/ directory for cross-session resume and compaction recovery.
  • Semi-Auto Fixes: Drives root-cause analysis and either implements isolated fixes or presents architectural tradeoff options for complex bugs.

Quick Start

Use the issue-triage skill to investigate GitHub issue number 419 by providing the issue number and letting it fetch, classify, and begin root-cause analysis.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I triage GitHub issues and identify probable code areas for bugs?▼

GitHub issue triage fetches issue data via gh, classifies bug reports and feature requests, and identifies probable code areas to transform raw reports into actionable investigation handoffs with file context.

What's the best way to perform root-cause analysis on untriaged GitHub bug reports?▼

Root-cause analysis on GitHub bug reports involves classifying the issue, identifying probable code areas, and either implementing isolated fixes or presenting architectural tradeoff options for complex bugs.

How do I create durable investigation handoffs for cross-session GitHub issue triage?▼

Durable investigation handoffs are written to the .claude/handoffs/ directory, capturing issue classification and file context to enable cross-session resume and compaction recovery during GitHub issue triage.

Does this issue triage workflow classify both bug reports and feature requests?▼

Yes, issue triage classifies GitHub issues into bug reports, features, and enhancements, then identifies probable code areas in the codebase to drive either semi-automatic fixes or architectural tradeoff presentations.

How do I start investigating a specific GitHub issue number end-to-end?▼

To investigate a specific GitHub issue, provide the issue number to the triage skill, which then fetches the issue data via gh, classifies it, and begins root-cause analysis with file context.

Can triage handle complex bugs that require architectural tradeoffs instead of direct fixes?▼

Yes, for complex bugs the triage process drives root-cause analysis and presents architectural tradeoff options rather than implementing isolated fixes, ensuring informed decision-making for JellyRock development.

Related Skills

Explore More Software Engineering Skills→
JnusoJnuso

github

Manage GitHub PRs, issues, and CI workflows via the gh CLI.

Community
Intermediate
TumeloRamaphosaTumeloRamaphosa

investigate

Investigate software failures through a four-phase evidence-first root-cause workflow.

Community
Advanced
jellyrockjellyrock
37

runtime-triage

Classify Roku BrightScript crash logs and generate investigation handoff packets.

Official
Advanced
gittowergittower
413

gh-issue

Create GitHub issues with repository-specific formatting and labels.

Official
Intermediate