New: 97,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

GitHub Bug Report Triage

by warpdotdev in warpdotdev/oz-skills

Triage GitHub bug reports for actionability. An agent skill from warpdotdev/oz-skills.

MITAuto-check passedTesting & QA

Install GitHub Bug Report Triage

skills CLI
$ npx skills add warpdotdev/oz-skills --skill github-bug-report-triage -a claude-code

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

GitHub CLI
$ gh skill install warpdotdev/oz-skills github-bug-report-triage --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/warpdotdev/oz-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/github-bug-report-triage .claude/skills/github-bug-report-triage && 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
github-bug-report-triage
GitHub stars
825
Token cost
~1.1k tokens
SKILL.md length
373 words
Files
2 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Triage GitHub bug reports for actionability. An agent skill from warpdotdev/oz-skills.

  • Works in 4 steps: Locate Issue Template → Evaluate Issue Quality → Make Determination → …
  • Evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter
  • SKILL.md covers Workflow and Examples
  • Reaches stackblitz.com

What it does

GitHub Bug Report Triage is an agent skill from warpdotdev/oz-skills. Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/ISSUE_TEMPLATE.md`).

It sits in Testing & QA, covering QA and bug reports. It works with GitHub. The licence is MIT.

When your agent uses it

  • Evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter
  • Tasks that involve QA and bug reports

Example prompts

  • “/github-bug-report-triage”

Workflow steps

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

  1. Locate Issue Template
  2. Evaluate Issue Quality
  3. Make Determination
  4. Provide Feedback

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • stackblitz.com

    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

GitHub Bug Report Triage loads about 1.1k tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 373 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

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 warpdotdev/oz-skills at commit 6c08c49, republished under its MIT licence (© warpdotdev). 373 words, ~1,072 tokens.

Download SKILL.mdSave it as .claude/skills/github-bug-report-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
github-bug-report-triage
description
Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.
license
MIT

GitHub Bug Report Triage

Evaluate GitHub issues for bug reports only. Determine if they contain sufficient info to be actionable. If not, identify missing details and provide constructive feedback.

Workflow

1. Locate Issue Template

Check for existing templates:

  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/ISSUE_TEMPLATE/*.md
  • .github/ISSUE_TEMPLATE.md
  • ISSUE_TEMPLATE.md

If no template exists, use references/ISSUE_TEMPLATE.md from this skill as the fallback template, then evaluate the issue against it.

2. Evaluate Issue Quality

Critical questions:

  1. Is this a bug report?

    • If the issue is a feature request or a question, do not evaluate this issue

  2. Is the description clear?

    • What's broken or wrong
    • Expected behavior vs. what actually happens
    • Impact or severity

  3. Can we reproduce it?

    • Step-by-step reproduction
    • OR sandbox/StackBlitz/CodeSandbox link
    • OR minimal code example

Be reasonable:

  • Don't require every template field to be filled
  • Focus on minimum info needed to investigate
  • Consider context (obvious bugs vs. edge cases)
3. Make Determination

Ready to be actionable:

  • Has clear problem description
  • Includes reproduction path OR enough context to debug
  • Actually a bug (not feature/question)

Needs more info:

  • Vague description ("it doesn't work")
  • Missing reproduction steps AND no code example
  • Unclear what the expected behavior should be
  • Missing critical context (e.g., "crashes" but no error message)
4. Provide Feedback

If ready: Confirm issue is actionable.

If needs info: Specify what's missing. Be constructive and specific.

Examples

Show full SKILL.md (153 more words)Show less
Example 1: Ready to Investigate
markdown
**Issue**: Dropdown menu doesn't close on mobile Safari

**Description**: 
When clicking a dropdown menu item on iOS Safari, the menu stays 
open instead of closing. Works fine on desktop Chrome/Firefox.

**Steps**:
1. Visit https://stackblitz.com/edit/my-repro
2. Open on iOS Safari
3. Click dropdown, select any item
4. Menu stays open (should close)

**Environment**: iOS 16.3, Safari

Evaluation: ✅ Ready

  • Clear description
  • Has reproduction link
  • Specific environment details
Example 2: Needs More Info
markdown
**Issue**: Button is broken

**Description**: 
The submit button doesn't work properly.

Evaluation: ❌ Needs info Missing:

  • What does "doesn't work" mean? (no click? error? wrong behavior?)
  • Expected vs. actual behavior
  • Steps to reproduce
  • Any error messages
Example 3: Edge Case - Reasonable
markdown
**Issue**: Console error on form submit

**Description**:
Getting "Cannot read property 'value' of null" when submitting 
the contact form. Happens 100% of the time.

**Error**:

TypeError: Cannot read property 'value' of null at handleSubmit (ContactForm.tsx:45)


**Environment**: Chrome 120, Windows 11

Evaluation: ✅ Ready

  • Clear error message with stack trace
  • Specific file/line reference
  • Reproducible (100% of time)
  • Note: No explicit repro steps, but error is clear enough to investigate
Example 4: Bug Report with Insufficient Reproducibility
markdown
**Issue**: [glob-loader] Duplicate id warning on file update

**Description**:
I'm encountering an issue with the glob loader. Whenever I update 
the watched file, I get a warning message in the logs.


The warning message:

13:23:31 [WARN] [glob-loader] Duplicate id "russian-test" found in /Users/user/Code/project/content/posts/russian-test.md. Later items with the same id will overwrite earlier ones.


**Expected**: No warning message

**Link to Minimal Reproducible Example**: - N/A

Evaluation: ❌ Needs info

  • Describes a real bug (warning message)
  • Has error output and code reference
  • BUT: No minimal reproduction provided
  • Code link points to private repo (can't access to debug)

Missing:

  • Minimal reproduction (example code or link to a working reproduction)

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

Files

SKILL.md and 1 other file (references) in .agents/skills/github-bug-report-triage of warpdotdev/oz-skills.

  • SKILL.md
  • references/ISSUE_TEMPLATE.md

Open the folder on GitHubat commit 6c08c49

Compare with similar skills

GitHub Bug Report 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.

GitHub Bug Report Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Bug Report Triage this skillwarpdotdev/oz-skills825—~1.1kAutomated safety check: PassMIT
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Create GitHub IssueNVIDIA/OpenShell15k—~1.7kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Gentle AI Issue CreationGentleman-Programming/gentle-shell1.2k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Gentle AI Issue Creation

    Gentleman-Programming/gentle-shell

    Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.

    1.2k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Termio Bug Report

    termio-sh/termio

    Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…

    540 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from warpdotdev/oz-skills

All 13 skills in this repo

  • SEO Aeo Audit

    warpdotdev/oz-skills

    Optimize for search engine visibility, ranking, and AI citations.

    825 GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Web Accessibility Audit

    warpdotdev/oz-skills

    Audit web applications for WCAG accessibility compliance. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~3.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Webapp Testing

    warpdotdev/oz-skills

    Test local web applications with Playwright. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~914 tokensUpdated 1 mo ago
    Auto-check passed

  • Analysis Artifacts

    warpdotdev/oz-skills

    Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • CI Fix

    warpdotdev/oz-skills

    Diagnose and fix GitHub Actions CI failures. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~790 tokensUpdated 1 mo ago
    Auto-check passed

  • Create Pull Request

    warpdotdev/oz-skills

    Create a GitHub pull request following project conventions. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about GitHub Bug Report Triage

What does GitHub Bug Report Triage do?

Triage GitHub bug reports for actionability. An agent skill from warpdotdev/oz-skills. GitHub Bug Report Triage is an agent skill from warpdotdev/oz-skills. Triage GitHub bug reports for actionability.

When should I use GitHub Bug Report Triage?

GitHub Bug Report Triage fits situations like: evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter; tasks that involve QA and bug reports.

How do I install GitHub Bug Report Triage in Claude Code?

Run `npx skills add warpdotdev/oz-skills --skill github-bug-report-triage -a claude-code`. Or copy the skill folder (.agents/skills/github-bug-report-triage in warpdotdev/oz-skills) into .claude/skills/github-bug-report-triage in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Bug Report Triage in Codex?

Run `npx skills add warpdotdev/oz-skills --skill github-bug-report-triage -a codex`. Or copy the skill folder (.agents/skills/github-bug-report-triage in warpdotdev/oz-skills) into .agents/skills/github-bug-report-triage in your project. Codex loads it when a task matches its description.

Can I use GitHub Bug Report 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 warpdotdev/oz-skills --skill github-bug-report-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/github-bug-report-triage, .gemini/skills/github-bug-report-triage, .github/skills/github-bug-report-triage and .opencode/skills/github-bug-report-triage in your project.

What does GitHub Bug Report Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: GitHub Bug Report Triage is instructions for the agent only.

Does GitHub Bug Report Triage access the network?

SKILL.md names 1 domain. In commands or code: stackblitz.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is GitHub Bug Report 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 GitHub Bug Report Triage use?

GitHub Bug Report Triage is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Bug Report Triage use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 158 tokens, read only when the agent opens those files.

What are the alternatives to GitHub Bug Report Triage?

Skills that share tags, products or a category with GitHub Bug Report Triage: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Bug Report Triage?

warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-skills, which has 825 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 15, 2026.

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