skills.rest
lugassawan
lugassawanCOMMUNITY
Explore all skills by this author →
GitHub

workflow-bug-triage

Investigate software defects and file structured GitHub issues with root-cause hypotheses.

2|8|Updated Apr 20, 2026
Search Tags:#root cause analysis#hypothesis testing#impact assessment#bug triage#github issue#debugging workflow#code path analysis
One-click install
npx skills add https://github.com/lugassawan/swe-workbench --skill workflow-bug-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-bug-triage
Source: https://github.com/lugassawan/swe-workbench/tree/main/skills/workflow-bug-triage
Command: npx skills add https://github.com/lugassawan/swe-workbench --skill workflow-bug-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you investigate a bug thoroughly and document the root cause so the right people can fix it later—without rushing into ungrounded patches.

Core Features & Use Cases

  • Iron Law guardrail: blocks “fix-first” behavior by requiring a root-cause hypothesis supported by evidence.
  • Structured 4-phase workflow: gathers context, contrasts working vs broken code paths, builds a single falsifiable hypothesis, and then files a shareable GitHub issue.
  • Issue quality tooling: prepares a code-path table and impact assessment in the issue body, using repo issue templates and labels when available.

Quick Start

Use workflow-bug-triage when you have a defect you want documented (not patched in-session) by asking it to investigate the root cause and file a GitHub bug report with reproduction, diagnosis, and impact.

Frequently Asked Questions about workflow-bug-triage

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

FAQPage Schema
How do I investigate a root cause and file a structured GitHub issue for a bug?▼

To investigate a root cause and file a GitHub issue, this skill runs a four-phase analysis loop to gather context, contrast code paths, build a falsifiable hypothesis, and generate a shareable bug report with reproduction steps.

What is the best way to document a bug for a separate fix instead of patching it in-session?▼

The best way to document a bug for a separate fix is to use a debugging workflow that blocks immediate patches and requires a reproduction-backed root-cause hypothesis before generating a structured issue with impact assessment.

How does hypothesis testing work during bug triage?▼

Hypothesis testing during bug triage works by contrasting working versus broken code paths to build a single falsifiable root-cause hypothesis, ensuring no fixes are applied without evidence-backed documentation.

Can I use repository issue templates and labels when filing a bug report?▼

Yes, you can use repository issue templates and labels. The skill prepares the issue body using available repository metadata, appending a code-path table and impact assessment upon user confirmation.

Why should I use a root-cause analysis workflow instead of applying direct code fixes?▼

You should use a root-cause analysis workflow instead of direct fixes because an iron law guardrail enforces a no-fixes-without-root-cause policy, ensuring defects are thoroughly documented for the right people to address later.

Does bug triage require a preview before confirming GitHub issue filing?▼

Yes, bug triage requires a preview gate before confirming GitHub issue filing. The workflow enforces a preview-then-confirm sequence using repository metadata to ensure accurate, shareable documentation.

Related Skills

Explore More Software Engineering Skills→
offlinecvofflinecv
8

create-gh-issue

Generate structured GitHub issues with root-cause analysis and implementation plans.

Official
Advanced
arvindbattulaarvindbattula

triage

Identify bug root causes and generate GitHub issues with TDD fix plans.

Community
Advanced
mozilor-technologiesmozilor-technologies

gitnexus

Analyze code dependencies and execution flows using precomputed knowledge graphs.

Official
Advanced
parcadeiparcadei
3.9k

morph-apply

Apply targeted file edits using code markers via Morph Apply API.

Community
Advanced