bug-start

Coordinate Firefox bug investigations and generate reproducible documentation.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill bug-start-alastor0325
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-start
Source: https://github.com/alastor0325/fx-bug-toolkit/tree/main/skills/bug-start
Command: npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill bug-start-alastor0325

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow provides a structured, repeatable approach to starting and documenting Firefox bug investigations, ensuring reproducible findings and traceable references.

Core Features & Use Cases

  • Guides you through collecting bug details, assessing failure patterns, citing sources with searchfox links, and generating a complete investigation document.
  • Supports triage and deep-investigation modes, metadata frontmatter, and the automatic creation of an investigation file for dashboards.

Quick Start

Run /bug-start <bug-id> to begin a full investigation of a Firefox bug.

Frequently Asked Questions about bug-start

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

FAQPage Schema
How do I start a structured Firefox bug investigation using Bugzilla data?

To start a structured Firefox bug investigation, run /bug-start <bug-id> to fetch Bugzilla data via MCP/bmo-to-md, collect evidence, and draft a reproducible investigation document with searchfox code citations.

What is the difference between triage and deep-investigation modes for bug analysis?

Triage mode assesses failure patterns and metadata for quick bug prioritization, while deep-investigation mode analyzes profiler profiles, identifies root causes, and drafts a full implementation plan.

How do I trace code references during a Bugzilla bug investigation?

Trace code references during a bug investigation by citing all relevant code with searchfox links, ensuring traceable references and reproducible findings in the final investigation document.

Can I analyze profiler profiles when investigating Firefox bugs?

Yes, you can analyze profiler profiles when present during a Firefox bug investigation. The workflow integrates profile analysis to help identify root causes and affected files.

What should a complete Firefox bug investigation report include?

A complete Firefox bug investigation report must include frontmatter metadata, root cause analysis, affected files, regression range, and an implementation plan, alongside generated locks and investigation files.