New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Triage Issue

by softspark in softspark/ai-toolkit

Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.

Apache-2.0Auto-check: notesDevelopment

Install Triage Issue

skills CLI
$ npx skills add softspark/ai-toolkit --skill triage-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install softspark/ai-toolkit triage-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app/skills/triage-issue .claude/skills/triage-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
triage-issue
GitHub stars
179
Token cost
~1.3k tokens
SKILL.md length
645 words
Files
1
Skills in repo
112
Repo updated
First seen
Licence
Apache-2.0

At a glance

Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.

  • Works in 5 steps: Capture the Problem → Explore and Diagnose → Identify Fix Approach → …
  • Tasks that involve Issue triage
  • SKILL.md covers Usage, What This Command Does, Process and Issue Template, plus 7 more sections
  • Calls gh and git

What it does

Triage Issue is an agent skill from softspark/ai-toolkit. Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage, Root cause analysis and Test-driven development. It works with GitHub. The repository describes itself as: Professional-grade AI coding toolkit: 94 skills, 44 agents, multi-platform (Claude, Cursor, Windsurf, Copilot, Gemini, Cline, Roo Code, Aider, Augment, Antigravity, Codex CLI… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Issue triage
  • Tasks that involve Root cause analysis
  • Tasks that involve Test-driven development

Example prompts

  • “/triage-issue”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, Agent

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Capture the Problem
  2. Explore and Diagnose
  3. Identify Fix Approach
  4. Design TDD Fix Plan
  5. Create GitHub Issue

What it can do on your machine

Read from SKILL.md and the folder at commit d64db2b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • Agent

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Triage Issue loads about 1.3k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 645 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, Agent

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from softspark/ai-toolkit at commit d64db2b, republished under its Apache-2.0 licence (© softspark). 645 words, ~1,256 tokens.

Download SKILL.mdSave it as .claude/skills/triage-issue/SKILL.md (or your agent's skills folder).
name
triage-issue
description
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report.
allowed-tools
Read, Grep, Glob, Bash, Agent
user-invocable
true
effort
high
argument-hint
[bug description or symptom]
agent
debugger
context
fork

Triage Issue

$ARGUMENTS

Investigate a bug, find root cause, and create a GitHub issue with a TDD fix plan. Mostly hands-off.

Usage

/triage-issue [bug description or symptom]

What This Command Does

  1. Captures problem description (ONE question max)
  2. Explores codebase deeply for root cause
  3. Identifies fix approach
  4. Designs TDD fix plan (RED→GREEN cycles)
  5. Creates GitHub issue via gh issue create

Process

1. Capture the Problem

Get brief description. If not provided, ask ONE question: "What's the problem you're seeing?"

Do NOT ask follow-up questions. Start investigating immediately.

2. Explore and Diagnose

Use Agent (subagent_type=Explore) to deeply investigate:

TargetWhat to look for
ManifestationWhere the bug appears (entry points, UI, API)
Code pathTrace the flow from trigger to symptom
Root causeWhy it fails (not just the symptom)
Related codeSimilar patterns, adjacent modules, existing tests
Recent changesgit log on relevant files
Working patternsSimilar code elsewhere that works correctly
3. Identify Fix Approach

Determine:

  • Minimal change to fix root cause
  • Affected modules/interfaces
  • Behaviors to verify via tests
  • Classification: regression, missing feature, or design flaw
4. Design TDD Fix Plan

Ordered list of RED→GREEN cycles. Each cycle is one vertical slice:

  • RED: Specific test capturing broken/missing behavior
  • GREEN: Minimal code change to pass that test

Rules:

  • Tests verify behavior through public interfaces
  • One test at a time, vertical slices
  • Tests must survive internal refactors
  • Describe behaviors and contracts, not internal structure
5. Create GitHub Issue

Use gh issue create with template below. Share URL immediately.

Issue Template

<issue-template>

Problem

  • What happens (actual behavior)
  • What should happen (expected behavior)
  • How to reproduce

Root Cause Analysis

What was found during investigation:

  • The code path involved
  • Why the current code fails
  • Contributing factors

Do NOT include file paths, line numbers, or implementation details. Describe modules, behaviors, and contracts.

TDD Fix Plan

  1. RED: Write test that [expected behavior] GREEN: [Minimal change to pass]

  2. RED: Write test that [next behavior] GREEN: [Minimal change to pass]

REFACTOR: [Cleanup after all tests pass]

Acceptance Criteria

  • Criterion 1
  • All new tests pass
  • Existing tests still pass
</issue-template>
Show full SKILL.md (303 more words)Show less

Rules

  • MUST explore the codebase for root cause before filing — symptoms masquerade as causes often
  • MUST propose a TDD fix plan with ordered RED→GREEN cycles, each a vertical slice
  • NEVER ask follow-up clarifying questions; one initial question maximum, then investigate autonomously
  • NEVER include file paths, function names, or line numbers in the issue body — they go stale before the issue is picked up
  • CRITICAL: the issue must be reproducible. If reproduction steps cannot be determined from the investigation, say so explicitly in the Problem section — do not fabricate them.
  • MANDATORY: file the issue immediately via gh issue create and share the URL — do not ask the user to review a draft first

Gotchas

  • gh issue create without --body opens $EDITOR. In automated flows the skill hangs — always pass the body file or inline text.
  • "Root cause" often turns out to be two concurrent issues. If the investigation keeps branching, file the most-probable primary cause and note the secondary as a follow-up in the same issue.
  • TDD plans with more than ~5 RED→GREEN cycles usually conceal a deeper design issue. Short plans (2-3 cycles) reflect confident root-cause identification; long plans reflect fishing.
  • The debugger agent explored autonomously but returns a narrative. Parse it for: confirmed hypothesis, code paths, and recent changes. Discard speculation.
  • Bugs in framework-adjacent code (middleware, ORM hooks) require test setup that mirrors the framework's call context. A TDD plan that writes the test "like a unit test" may not actually reproduce the framework bug.

When NOT to Use

  • For a conversational bug report from a non-engineer — use /qa-session first, which returns refined reports this skill can then process
  • For a specific reproducible error with known root cause — use /fix directly
  • For architectural-scale problems — use /architecture-audit
  • For creating issues from a PRD — use /prd-to-issues
  • For debugging without filing an issue — use /debug

© softspark, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in app/skills/triage-issue of softspark/ai-toolkit.

Open the folder on GitHubat commit d64db2b

Compare with similar skills

Triage Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Triage Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Issue this skillsoftspark/ai-toolkit179—~1.3kAutomated safety check: NotesApache-2.0
Triagebot Action Bug Triagewithastro/astro63k—~639Automated safety check: PassCustom licence
OpenROAD Issue TriageThe-OpenROAD-Project/OpenROAD3.2k—~842Automated safety check: PassBSD-3-Clause
Issue TracerZaxbyHub/opencode-swarm490—~4.4kAutomated safety check: PassMIT
Prp DebugWirasm/prp2.3k—~1.1kAutomated safety check: PassMIT
Prp DebugWirasm/prp2.3k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Triagebot Action Bug Triage

    withastro/astro

    Official

    Takes a bug report for the triagebot-action GitHub Action through reproduction, root-cause diagnosis, an intended-behavior check and a fix attempt.

    63k GitHub stars~639 tokensUpdated today
    DevelopmentAuto-check passed

  • OpenROAD Issue Triage

    The-OpenROAD-Project/OpenROAD

    Reproduces an OpenROAD GitHub bug from an attached tarball and shrinks the failing design with whittle.py so maintainers get a minimal test case.

    3.2k GitHub stars~842 tokensUpdated today
    DevelopmentAuto-check passed

  • Issue Tracer

    ZaxbyHub/opencode-swarm

    Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.

    490 GitHub stars~4.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Prp Debug

    Wirasm/prp

    Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

    2.3k GitHub stars~1.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Prp Debug

    Wirasm/prp

    Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

    2.3k GitHub stars~1.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • LazyCodex Bug Reporter

    code-yeongyu/oh-my-openagent

    Investigates a LazyCodex or Codex CLI defect, decides which GitHub repository owns it, and drafts an evidence-backed issue or pull request with repro steps.

    70k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

More from softspark/ai-toolkit

All 112 skills in this repo

  • Prepare Test Env

    softspark/ai-toolkit

    Prepare or verify a project QA environment with source identity, readiness, browser access, evidence paths and owned cleanup.

    179 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes

  • A11y Validate

    softspark/ai-toolkit

    Accessibility validator: WCAG 2.1 AA, EN 301 549, EAA. An agent skill from softspark/ai-toolkit.

    179 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check: notes

  • Analyze

    softspark/ai-toolkit

    Analyzes code quality, complexity, patterns across codebase.

    179 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Autonomous Dev

    softspark/ai-toolkit

    Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR.

    179 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes

  • Brand Voice

    softspark/ai-toolkit

    Direct technical voice for docs, README, user-facing text. An agent skill from softspark/ai-toolkit.

    179 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • CI

    softspark/ai-toolkit

    Detect/generate/debug CI pipeline config (GitHub Actions, GitLab CI).

    179 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Triage Issue

What does Triage Issue do?

Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triage Issue is an agent skill from softspark/ai-toolkit. Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.

When should I use Triage Issue?

Triage Issue fits situations like: tasks that involve Issue triage; tasks that involve Root cause analysis; tasks that involve Test-driven development.

How do I install Triage Issue in Claude Code?

Run `npx skills add softspark/ai-toolkit --skill triage-issue -a claude-code`. Or copy the skill folder (app/skills/triage-issue in softspark/ai-toolkit) into .claude/skills/triage-issue in your project. Claude Code loads it when a task matches its description.

How do I install Triage Issue in Codex?

Run `npx skills add softspark/ai-toolkit --skill triage-issue -a codex`. Or copy the skill folder (app/skills/triage-issue in softspark/ai-toolkit) into .agents/skills/triage-issue in your project. Codex loads it when a task matches its description.

Can I use Triage Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add softspark/ai-toolkit --skill triage-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-issue, .gemini/skills/triage-issue, .github/skills/triage-issue and .opencode/skills/triage-issue in your project.

What does Triage Issue need to run?

Going by SKILL.md and its folder, Triage Issue needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Agent.

Does Triage Issue access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Triage Issue safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Triage Issue use?

Triage Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Triage Issue use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Triage Issue?

Skills that share tags, products or a category with Triage Issue: Triagebot Action Bug Triage (withastro/astro, 63k stars), OpenROAD Issue Triage (The-OpenROAD-Project/OpenROAD, 3.2k stars), Issue Tracer (ZaxbyHub/opencode-swarm, 490 stars) and Prp Debug (Wirasm/prp, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage Issue?

softspark (a GitHub user) maintains it in softspark/ai-toolkit, which has 179 GitHub stars. The repository holds 112 skills in this directory. The repository was last updated on October 7, 2026.

Source: softspark/ai-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.