
github-bug-report-triage
Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.
- Installs
- 382
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/warpdotdev/oz-skills --skill github-bug-report-triage- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads github-bug-report-triage automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.mdISSUE_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:
-
Is this a bug report?
- If the issue is a feature request or a question, do not evaluate this issue
-
Is the description clear?
- What's broken or wrong
- Expected behavior vs. what actually happens
- Impact or severity
-
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
**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
**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
**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
**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)
FAQ
What does the github-bug-report-triage skill do?
Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.
How do I install github-bug-report-triage?
Run npx skills add https://github.com/warpdotdev/oz-skills --skill github-bug-report-triage in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/github-bug-report-triage/ (personal) or .claude/skills/github-bug-report-triage/ (project).
Which AI agents can use github-bug-report-triage?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is github-bug-report-triage safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains github-bug-report-triage?
It is published by warpdotdev in warpdotdev/oz-skills. It has 382 recorded installs.
More from warpdotdev/oz-skills
seo-aeo-audit
warpdotdev/oz-skills
Optimize for search engine visibility, ranking, and AI citations. Use when asked to improve SEO, optimize for search, fix meta tags, add structured data, or improve AEO and AI visibility.
scheduler
warpdotdev/oz-skills
Schedule on-device reminders and local actions only. Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval (e.g., notifications, local scripts), on the user's computer or with platforms like Slack. Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows.
ci-fix
warpdotdev/oz-skills
Open the skill to read its SKILL.md instructions.
docs-update
warpdotdev/oz-skills
Update user-facing documentation when code changes. Use when asked to update docs, review docs, handle documentation changes, run scheduled documentation tasks, or analyze recent commits for documentation needs.
web-accessibility-audit
warpdotdev/oz-skills
Audit web applications for WCAG accessibility compliance. Use when asked to run accessibility checks, identify common violations, and provide remediation guidance.
web-performance-audit
warpdotdev/oz-skills
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.