bug-chaser

Triage bug reports into engineering tickets with validated reproduction steps.

8|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/officebeats/beats-pm-antigravity-brain --skill bug-chaser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-chaser
Source: https://github.com/officebeats/beats-pm-antigravity-brain/tree/main/.agent/skills/bug-chaser
Command: npx skills add https://github.com/officebeats/beats-pm-antigravity-brain --skill bug-chaser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Bug Chaser skill acts as a Quality Gate for bug reports, ensuring that only well-defined issues with reproduction steps, clear severity, and evidence enter the backlog, turning chaos into trackable work items.

Core Features & Use Cases

  • Enforces the Triad of Truth (Steps, Expected, Actual) during bug reports.
  • Applies SLA-oriented severity mapping (P0–P3) and auto-routes to engineering when warranted.
  • Logs issues consistently to the master tracker and creates actionable tickets for Eng.

Quick Start

Triaging a bug report by extracting steps to reproduce, expected and actual outcomes, classifying severity, and creating a corresponding engineering ticket.

Frequently Asked Questions about bug-chaser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage bug reports into actionable engineering tickets?

Bug triage enforces the Triad of Truth by validating reproduction steps, expected outcomes, and actual outcomes. This mechanism ensures only reports with clear evidence and severity enter the backlog as trackable work items.

How does severity mapping work for bug triage?

Bug triage requires a defined triage workflow, a severity mapping strategy from P0 to P3, and a master log file. You also need engineering partners designated for routing the validated tickets.

Can I use this for fast triage of bug reports with reproduction steps?

Yes, fast triage applies to bug reports containing reproduction steps, severity, evidence, and ownership. It routes validated issues to engineering partners and records them in a master log file.

How do I log triaged issues to a master tracker?

Triaged issues are logged consistently to a master tracker file to maintain a centralized backlog. This creates trackable work items and ensures validated bug reports are recorded for engineering follow-up.

What is the best way to enforce reproduction steps in bug reports?

The best way to enforce reproduction steps is applying the Triad of Truth, which requires steps, expected outcomes, and actual outcomes. This quality gate prevents poorly defined issues from entering the backlog.