Agent Native

github-bug-report-triage

This skill evaluates GitHub bug reports to determine if they contain sufficient information for investigation.

by warpdotdevCommunityNot reviewed

Community author

Agents
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, claude.ai and API
License
MIT (permissive)
Pin
6c08c49pinned Oct 9, 2026
Context cost
about 1,000 tokenswhen the skill loads
GitHub stars
825on warpdotdev/oz-skills
Scripts
None found

What it does

“Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.”
The author's description, from SKILL.md

Generated summary from the skill's own text

This skill evaluates GitHub bug reports to determine if they contain sufficient information for investigation. It checks issues against project templates, assesses reproduction steps and clarity, then provides feedback on whether the report is actionable or what details are missing.

When to use it

  • Triaging incoming GitHub issues to prioritize actionable bug reports
  • Identifying incomplete bug reports needing more information from reporters
  • Enforcing consistent issue quality standards in repositories
  • Reviewing issues before assigning them to development teams

When not to

  • Evaluating feature requests or discussion issues instead of bugs
  • Assessing issues without access to the repository or templates
  • Automating fixes based on bug report content

Install

These commands install from the publisher's repository and need no account.

skills CLI

npx skills add warpdotdev/oz-skills --skill github-bug-report-triage

Installs from the repository's default branch, which may have changed since the commit we checked.

GitHub CLI 2.90 or later

gh skill install warpdotdev/oz-skills github-bug-report-triage@6c08c49fc6c51b8f768bf8c53c041bc06a160765

Installs the commit we checked (6c08c49).

Copy by hand

Download the folder at 6c08c49 and put it in .claude/skills/github-bug-report-triage for Claude Code and in .agents/skills/github-bug-report-triage for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.

Skill folder on GitHub at 6c08c49

Copy for your agent

A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.

Prompt

Install the agent skill "github-bug-report-triage" by warpdotdev.

Source, pinned to commit 6c08c49fc6c51b8f768bf8c53c041bc06a160765:
https://github.com/warpdotdev/oz-skills/tree/6c08c49fc6c51b8f768bf8c53c041bc06a160765/.agents/skills/github-bug-report-triage

1. Download that folder at exactly this commit. Do not use the default branch.
2. Copy every file unchanged, keeping the folder structure, into .claude/skills/github-bug-report-triage/ for Claude Code and .agents/skills/github-bug-report-triage/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist.
3. Do not edit the files, and do not run any script in the folder unless I ask you to.
4. When you are done, list the files you copied and where you put them.

Listing and checks: https://www.agentnative.dev/skills/warpdotdev/github-bug-report-triage

SKILL.md at the pin

---
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

### 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)

From warpdotdev/oz-skills at 6c08c49, shown as plain text under its license: MIT (permissive). The license text is in .agents/skills/github-bug-report-triage/SKILL.md.

View SKILL.md on GitHub at 6c08c49

Files

2 files, 4.9 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.

Skill folder on GitHub at 6c08c49
All Coding workflow skills
  • maintainer-review

    This skill helps maintainers assess GitHub issues and PRs by evaluating whether claimed problems are real, whether existing features already solve them, and…

    by OpenAIOfficial publisher

    Claude Code, Codex, Cursor +4 · about 8.9K tokens · pinned 6 days ago

  • maintainer-review

    Evaluates GitHub issues and PRs through a systematic desk review to assess demonstrated need, existing workarounds, design correctness, and maintainer impact.

    by OpenAIOfficial publisher

    Claude Code, Codex, Cursor +4 · about 8.3K tokens · pinned 6 days ago

  • dd-file-issue

    This skill helps file GitHub issues to the DataDog/pup repository for bugs, feature requests, and documentation problems related to the pup CLI, agents, and…

    by DatadogOfficial publisher

    Claude Code, Codex, Cursor +3 · about 2.2K tokens · pinned 6 days ago

  • create-pr

    This skill creates a GitHub pull request with a Linear-ticket-prefixed title and a decision-led narrative description for the prisma-next repository.

    by PrismaOfficial publisher

    Claude Code, Codex, Cursor +4 · about 4.3K tokens · pinned 6 days ago

  • github-review-iteration

    Orchestrates an iterative GitHub PR review loop by delegating triage and implementation to sub-agents, then repeating until all actionable review items are…

    by PrismaOfficial publisher

    Contains scripts

    Claude Code · about 1.9K tokens · pinned 6 days ago

  • prisma-next-feedback

    Routes bug reports, feature requests, and team Q&A to the appropriate Prisma Next channel.

    by PrismaOfficial publisher

    Claude Code, Codex, Cursor +4 · about 4.2K tokens · pinned 6 days ago

The skills listed here are third-party software, collected from public GitHub repositories as a catalog of recent skills and provided as is. Agent Native does not write or control them and is not responsible for any harm, loss or damage caused by installing or using them. Labels and checks describe what we saw at one commit and are not a guarantee. Read a skill's files before you run it. Terms of use