skills.rest
sequenzia
sequenziaCOMMUNITY
Explore all skills by this author →
Website𝕏@sequenziaGitHub

bug-killer

Automate hypothesis-driven debugging with triage-based routing and agent coordination.

2|Updated Mar 9, 2026
Search Tags:#debugging#agents#code-analysis#phases#hypothesis#bug-investigation
One-click install
npx skills add https://github.com/sequenzia/agent-tools --skill bug-killer-sequenzia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-killer
Source: https://github.com/sequenzia/agent-tools/tree/main/plugins/core/skills/bug-killer
Command: npx skills add https://github.com/sequenzia/agent-tools --skill bug-killer-sequenzia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex issues often drains time and guesswork. Bug Killer enforces a structured, hypothesis-driven workflow with five phases to ensure investigation precedes fixes and produces a clear wrap-up report.

Core Features & Use Cases

  • Five-phase debugging orchestration: Triage & Reproduction, Investigation, Root Cause Analysis, Fix & Verify, and Wrap-up & Report.
  • Agent coordination: spawn bug-investigator subagents and code-exploration tasks to gather evidence without applying changes.
  • Hypothesis journal and structured documentation to capture learnings and guide future fixes.

Quick Start

Provide a bug description and context to initiate Phase 1 triage and start the hypothesis-driven investigation.

Frequently Asked Questions about bug-killer

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

FAQPage Schema
How do I debug complex code failures using a hypothesis-driven workflow?▼

A hypothesis-driven debugging workflow automates bug investigation by routing triage through five phases: reproduction, investigation, root cause analysis, fix, and report. You provide bug context and environment details to start the structured process.

What is the best way to track down a bug before applying code fixes?▼

The best way to track down a bug before fixing is using a structured investigation workflow that spawns bug-investigator subagents and code-exploration tasks to gather evidence, ensuring root cause analysis precedes any code changes.

How do I conduct a full investigation when a bug is difficult to reproduce?▼

To conduct a full investigation for difficult bugs, you initiate a deep debugging workflow that enforces triage-based routing and coordinates an agent network across five phases to methodically gather evidence and identify the root cause.

Do I need an agent network to run a structured code-analysis debugging workflow?▼

Yes, you need an agent network with bug-investigator and code-exploration capabilities to execute the hypothesis-driven debugging phases and gather evidence without applying changes directly to the codebase.

What limitations should I expect when using an automated bug-investigation workflow?▼

An automated bug-investigation workflow requires clear bug context and environment details upfront to function correctly; without accurate initial information, the hypothesis-driven phases may fail to identify the correct root cause for complex issues.

Related Skills

Explore More Software Engineering Skills→
equinorequinor
9

fusion-issue-author-bug

Draft and update structured GitHub bug issues with validated labels.

Official
Intermediate
jimiryquaijimiryquai

compound

Document solved problems with root cause and AS-IS/TO-BE states.

Community
Intermediate
vinhnxvvinhnxv
6

debug

Coordinate parallel hypothesis-investigator agents for ACH-based bug debugging.

Community
Advanced
robertbr123robertbr123

systematic-debugging

Debug system failures using a 4-phase root cause methodology.

Community
Advanced