Issue Triage Workflow
Hack23/cia
Triage GitHub issues: labeling, prioritization, assignment, and resolution tracking
Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file.
Install Bug Triage
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios bug-triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/bug-triage .claude/skills/bug-triage && rm -rf skills-srcUse ~/.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/
Install the "bug-triage" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage into .claude/skills/bug-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios bug-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/bug-triage .agents/skills/bug-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bug-triage" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage into .agents/skills/bug-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios bug-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/bug-triage .cursor/skills/bug-triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bug-triage" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage into .cursor/skills/bug-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Donchitos/Claude-Code-Game-Studios.git --path .claude/skills/bug-triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios bug-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/bug-triage .gemini/skills/bug-triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bug-triage" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage into .gemini/skills/bug-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Donchitos/Claude-Code-Game-Studios bug-triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/bug-triage .github/skills/bug-triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bug-triage" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage into .github/skills/bug-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios bug-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/bug-triage .opencode/skills/bug-triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bug-triage" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage into .opencode/skills/bug-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
bug-triage- GitHub stars
- 26k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 945 words
- Files
- 1
- Skills in repo
- 73
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file.
- Works in 6 steps: Parse Arguments → Load Bug Backlog → Classify Each Bug → …
- Starting a sprint and deciding which open bugs go into it
- SKILL.md covers 1. Parse Arguments, 2. Load Bug Backlog, 3. Classify Each Bug and 4. Trend Analysis, plus 3 more sections
- Calls bash
What it does
This skill turns a pile of open bug reports into a prioritized, sprint-assigned list. It finds bugs in `production/qa/bugs/` first, then in a single `bugs.md` log, then in QA plan tables, and stops with nothing to triage if none exist. It treats severity (how bad the impact is) and priority (how soon it must be fixed) as separate judgments, looks for systemic patterns and makes sure no critical bug is dropped between sprints.
Three modes are available: `/bug-triage sprint` assigns fixable bugs to the current sprint and defers the rest, `full` triages everything regardless of sprint, and `trend` is a read-only analysis that reads only header fields such as severity, priority, status, system and date. With no argument it uses sprint mode if a sprint exists. A project automation setting decides whether it asks about every question and file write, only major ones, or logs and proceeds. The result is saved as a dated markdown file under `production/qa/`.
When your agent uses it
- Starting a sprint and deciding which open bugs go into it
- Re-evaluating bug priority after new reports follow a QA pass
- Spotting systemic trends across systems or categories when the open count passes 10
Example prompts
- “Run /bug-triage sprint and assign what we can fix this sprint.”
- “Do a full triage of every open bug, ignoring sprint scope.”
- “Give me a trend-only report on bug severity by system, without changing anything.”
Requirements
- Bug reports kept as markdown files under production/qa/bugs
- Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit, Bash(bash "*/.claude/skills/bug-triage/../../hooks/yaml-helper.sh" resolve_config *)
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b21fa0f. 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:
ReadGlobGrepWriteEditBash(bash "*/.claude/skills/bug-triage/../../hooks/yaml-helper.sh" resolve_config *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Bug Triage loads about 2.3k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 945 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 Donchitos/Claude-Code-Game-Studios at commit b21fa0f, republished under its MIT licence (© Donchitos). 945 words, ~2,300 tokens.
Download SKILL.mdSave it as
.claude/skills/bug-triage/SKILL.md (or your agent's skills folder).- name
- bug-triage
- description
- Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
- allowed-tools
- Read, Glob, Grep, Write, Edit, Bash(bash "*/.claude/skills/bug-triage/../../hooks/yaml-helper.sh" resolve_config *)
- argument-hint
- [sprint | full | trend]
- user-invocable
- true
- model
- sonnet
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Bug Triage
This skill processes the open bug backlog into a prioritised, sprint-assigned action list. It distinguishes between severity (how bad is the impact?) and priority (how urgently must we fix it?), detects systemic trends, and ensures no critical bug is lost between sprints.
Output: production/qa/bug-triage-[date].md
When to run:
- Sprint start — assign open bugs to the new sprint or backlog
- After
/team-qacompletes and new bugs have been filed - When the bug count crosses 10+ open items
1. Parse Arguments
Modes:
/bug-triage sprint— triage against the current sprint; assign fixable bugs to the sprint backlog; defer the rest/bug-triage full— full triage of all bugs regardless of sprint scope/bug-triage trend— trend analysis only (no assignment); read-only report- No argument — run sprint mode if a current sprint exists, else full mode
2. Load Bug Backlog
Step 2a — Discover bug files
Glob for bug reports in priority order:
production/qa/bugs/*.md— individual bug report files (preferred format)production/qa/bugs.md— single consolidated bug log (fallback)- Any
production/qa/qa-plan-*.md"Bugs Found" table (last resort)
If no bug files found:
"No bug files found in
production/qa/bugs/. If bugs are tracked in a different location, adjust the glob pattern. If no bugs exist yet, there is nothing to triage."
Stop and report. Do not proceed if no bugs exist. Verdict: COMPLETE — no bug files in production/qa/bugs/; nothing to triage.
In trend mode, do not read full bug bodies. Trend metrics (volume, severity
mix, by-system, by-date) are computable from the header fields alone:
Grep pattern="\*\*(Severity|Priority|Status|System|Category|Reported)\*\*" glob="production/qa/bugs/*.md" output_mode="content"(Bug-report fields are bolded — **Severity**:, - **System**: — so match the
**field** form, not a bare line-start Field:.)
Full bug bodies are needed only for the priority-vs-severity re-evaluation in
sprint/full modes; trend is a read-only report and skips it. (The one
deviation check that needs a story's status — "bug filed against a Complete
story" — is a targeted story-status grep either way, not a bug-body read.)
Step 2b — Load sprint context
Read the most recently modified file in production/sprints/ to understand:
- Current sprint number / name
- Stories in scope (for assignment target)
- Sprint capacity constraints (if noted)
If no sprint file exists: note "No sprint plan found — assigning to backlog only."
Step 2c — Load severity reference
Read .claude/docs/coding-standards.md for severity/priority definitions if they
exist. If they do not exist, use the standard definitions in Step 3.
3. Classify Each Bug
For each bug, extract or infer:
Severity (impact of the bug)
| Severity | Definition |
|---|---|
| S1 — Critical | Game crashes, data loss, or complete feature failure. Cannot proceed past this point. |
| S2 — High | Major feature broken but game is still playable. Significant wrong behaviour. |
| S3 — Medium | Feature degraded but a workaround exists. Minor wrong behaviour. |
| S4 — Low | Visual glitch, cosmetic issue, typo. No gameplay impact. |
Priority (urgency of the fix)
| Priority | Definition |
|---|---|
| P1 — Fix this sprint | Blocks QA, blocks release, or is regression from last sprint |
| P2 — Fix soon | Should be resolved before the next major milestone |
| P3 — Backlog | Would be good to fix, but no active blocking impact |
| P4 — Won't fix / Deferred | Accepted risk or out of scope for current product scope |
Show full SKILL.md (408 more words)Show less
Assignment
For each P1/P2 bug in sprint mode:
- Identify which story or epic the fix belongs to
- Check whether the current sprint has remaining capacity
- If capacity exists: assign to sprint (
Sprint: [current]) - If capacity is full: flag as
Priority overflow — consider pulling from sprint
For full mode: assign all P1 to current sprint, P2 to next sprint estimate,
P3+ to backlog.
Deviation check
Flag bugs that suggest systematic problems:
- 3+ bugs from the same system in the same sprint → "Potential design or implementation quality issue in [system]"
- 2+ S1/S2 bugs in the same story → "Story may need to be reopened and re-reviewed before shipping"
- Bug filed against a story marked Complete → "Regression in completed story — story should be re-opened in sprint tracking"
4. Trend Analysis
After classifying all bugs, generate trend metrics:
Volume trends
- Total open bugs: [N]
- Opened this sprint: [N]
- Closed this sprint: [N]
- Net change: [+N / -N]
System hot spots
- Which system has the most open bugs?
- Which system has the highest S1/S2 ratio?
Age analysis
- How many bugs are older than 2 sprints?
- Are any S1/S2 bugs un-assigned (sprint = none)?
Regression indicator
- Any bugs filed against previously-completed stories?
- Count: [N] regression bugs (story reopened implied)
5. Generate Triage Report
# Bug Triage Report
> **Date**: [date]
> **Mode**: [sprint | full | trend]
> **Generated by**: /bug-triage
> **Open bugs processed**: [N]
> **Sprint in scope**: [sprint name, or "N/A"]
---
## Triage Summary
| Priority | Count | Notes |
|----------|-------|-------|
| P1 — Fix this sprint | [N] | [N] assigned to sprint, [N] overflow |
| P2 — Fix soon | [N] | Scheduled for next sprint |
| P3 — Backlog | [N] | Deferred |
| P4 — Won't fix | [N] | Accepted risk |
**Critical (S1/S2) unfixed count**: [N]
---
## P1 Bugs — Fix This Sprint
| ID | System | Severity | Summary | Assigned to | Story |
|----|--------|----------|---------|-------------|-------|
| BUG-NNNN | [system] | S[1-4] | [one-line description] | [sprint] | [story path] |
---
## P2 Bugs — Fix Soon
| ID | System | Severity | Summary | Target Sprint |
|----|--------|----------|---------|---------------|
| BUG-NNNN | [system] | S[1-4] | [one-line description] | Sprint [N+1] |
---
## P3/P4 Bugs — Backlog / Won't Fix
| ID | System | Severity | Summary | Disposition |
|----|--------|----------|---------|-------------|
| BUG-NNNN | [system] | S4 | [one-line description] | Backlog |
---
## Systemic Issues Flagged
[List any patterns from Step 3 deviation check, or "None identified."]
---
## Trend Analysis
**Volume**: [N] open / [+N] net change this sprint
**Hot spot**: [system with most bugs]
**Regressions**: [N] bugs against completed stories
**Aged bugs (>2 sprints old)**: [N]
[If N aged S1/S2 bugs > 0:]
> ⚠️ [N] high-severity bugs have been open for more than 2 sprints without
> assignment. These represent accepted risk that should be explicitly reviewed.
---
## Recommended Actions
1. [Most urgent action — usually "fix P1 bugs before QA hand-off"]
2. [Second action — usually "investigate [hot spot system] quality"]
3. [Third action — optional improvement]6. Write and Gate
Present the report in conversation. If any bug is a P4 candidate, first ask
"Are these acceptable as Won't Fix?" and keep its disposition P4 candidate
until the user answers. Then ask:
"May I write this triage report to production/qa/bug-triage-[date].md?"
Write only after approval.
After writing:
- If any S1 bugs are unassigned: "S1 bugs must be assigned before the sprint
can be considered healthy. Run
/sprint-statusto see current capacity." - If regression bugs exist: "Regressions found — consider re-opening the
affected stories in sprint tracking and running
/smoke-checkto re-gate." - If no P1 bugs exist: "No P1 bugs — build is in good shape for QA hand-off."
Then, whether or not P1 bugs exist: Verdict: COMPLETE — triage report written.
If user declined write: Verdict: BLOCKED — user declined write.
Collaborative Protocol
- Never close or mark bugs Won't Fix without user approval — surface them as P4 candidates and ask: "Are these acceptable as Won't Fix?"
- Never auto-assign to a sprint at capacity — flag overflow and let the sprint owner decide what to pull
- Severity is objective; priority is a team decision — present severity classifications as recommendations, not mandates
- Trend data is informational — do not block work on trend findings alone; surface them as observations
© Donchitos, MIT. 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 .claude/skills/bug-triage of Donchitos/Claude-Code-Game-Studios.
Open the folder on GitHubat commit b21fa0f
Compare with similar skills
Bug Triage 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bug Triage this skillDonchitos/Claude-Code-Game-Studios | 26k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Issue Triage WorkflowHack23/cia | 239 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Priority Score Calculatormaslennikov-ig/claude-code-orchestrator-kit | 259 | — | ~1k | Automated safety check: Pass | Custom licence | |
| GitHub Project Management Swarmruvnet/agentic-flow | 816 | 6 repos | ~7.1k | Automated safety check: Pass | None | |
| Bug Report TriageOrchestratorInc/agent-orchestrator | 13k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| OpenROAD Issue TriageThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~842 | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Priority Score Calculator
maslennikov-ig/claude-code-orchestrator-kit
Scores a bug, issue or task from severity, impact and likelihood on a 0-30 scale and maps the total to a P0 to P4 priority category with a suggested action.
GitHub Project Management Swarm
ruvnet/agentic-flow
Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.
Bug Report Triage
OrchestratorInc/agent-orchestrator
Helps a reporter describe a bug, searches for duplicates and gathers diagnostic evidence kept separate from a short, human-worded issue draft.
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.
Bmad Investigate
aj-geddes/claude-code-bmad-skills
Forensic bug and issue triage. An agent skill from aj-geddes/claude-code-bmad-skills.
More from Donchitos/Claude-Code-Game-Studios
All 73 skills in this repoGame Asset Audit
Donchitos/Claude-Code-Game-Studios
Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.
Game Asset Spec Writer
Donchitos/Claude-Code-Game-Studios
Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.
Game Balance Check
Donchitos/Claude-Code-Game-Studios
Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.
Structured Bug Reports
Donchitos/Claude-Code-Game-Studios
Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.
Changelog Generator for Games
Donchitos/Claude-Code-Game-Studios
Generates an internal or player-facing changelog from git commits and sprint data, filtering out framework maintenance commits so that only work on the game itself reaches release copy.
Architectural Code Review
Donchitos/Claude-Code-Game-Studios
Performs an architectural review of code against coding standards, SOLID, testability and performance, and reports no verdict when the inputs are missing.
Related
Categories
Questions about Bug Triage
What does Bug Triage do?
Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file. This skill turns a pile of open bug reports into a prioritized, sprint-assigned list.md` log, then in QA plan tables, and stops with nothing to triage if none exist.
When should I use Bug Triage?
Bug Triage fits situations like: starting a sprint and deciding which open bugs go into it; re-evaluating bug priority after new reports follow a QA pass; spotting systemic trends across systems or categories when the open count passes 10.
How do I install Bug Triage in Claude Code?
Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a claude-code`. Or copy the skill folder (.claude/skills/bug-triage in Donchitos/Claude-Code-Game-Studios) into .claude/skills/bug-triage in your project. Claude Code loads it when a task matches its description.
How do I install Bug Triage in Codex?
Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill bug-triage -a codex`. Or copy the skill folder (.claude/skills/bug-triage in Donchitos/Claude-Code-Game-Studios) into .agents/skills/bug-triage in your project. Codex loads it when a task matches its description.
Can I use Bug Triage 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 Donchitos/Claude-Code-Game-Studios --skill bug-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-triage, .gemini/skills/bug-triage, .github/skills/bug-triage and .opencode/skills/bug-triage in your project.
What does Bug Triage need to run?
Going by SKILL.md and its folder, Bug Triage needs the command-line tools its instructions call (bash). Our summary lists: Bug reports kept as markdown files under production/qa/bugs. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit, Bash(bash "*/.claude/skills/bug-triage/../../hooks/yaml-helper.sh" resolve_config *).
Does Bug Triage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Bug Triage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Bug Triage use?
Bug Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bug Triage use?
About 2.3k tokens (SKILL.md is roughly 9.2k 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 Bug Triage?
Skills that share tags, products or a category with Bug Triage: Issue Triage Workflow (Hack23/cia, 239 stars), Priority Score Calculator (maslennikov-ig/claude-code-orchestrator-kit, 259 stars), GitHub Project Management Swarm (ruvnet/agentic-flow, 816 stars) and Bug Report Triage (OrchestratorInc/agent-orchestrator, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bug Triage?
Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 25,834 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on September 29, 2026.
Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.