Github Bug Report Triage logo

Github Bug Report Triage

Organization
warpdotdev
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.

Overview

Publisherwarpdotdev
Repositoryoz-skills
Skill namegithub-bug-report-triage
Stars
824
Forks
68
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by warpdotdev on GitHub. Read the source before you install it.

Installation

Install the Github Bug Report Triage AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/warpdotdev/oz-skills/tree/main/.agents/skills/github-bug-report-triage
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/warpdotdev/oz-skills.git /tmp/oz-skills
mkdir -p .claude/skills
cp -r /tmp/oz-skills/.agents/skills/github-bug-report-triage .claude/skills/github-bug-report-triage
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Github Bug Report Triage in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Github Bug Report Triage on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Github Bug Report Triage is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Github Bug Report Triage AI 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.

Why use Github Bug Report Triage on TypingMind?

Because you install it once and use it with any model. Github Bug Report Triage is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Github Bug Report Triage in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/warpdotdev/oz-skills/tree/main/.agents/skills/github-bug-report-triage. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Github Bug Report Triage?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Github Bug Report Triage?

As many as you like. As long as a model supports skills, you can use Github Bug Report Triage with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Github Bug Report Triage AI skill free?

Yes. It is published on GitHub by warpdotdev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇