agentsclimarketplace

Speckit.debug

Skill wedabro/bro-skills/.agents/skills/speckit.debug

bro-skills - Spec-Driven Development CLI

Install
npx -y skills add wedabro/bro-skills --skill speckit.debug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Systematic Debugger - Diagnose problems, find individual root causes, and recommend fix plans.

SKILL.md

1.5 KB, 325 tokens by cl100k_base, as published. Nobody here has run it

🎯 Mission

Use scientific methodology to find the root cause of bugs without disturbing the main context of feature development.

📋 Protocol

Phase 1: Symptom Gathering (Symptom collection)

Before starting to code, make it clear:

  • Expected behavior: What is the expected result?
  • Actual behavior: What is the actual result that is happening?
  • Error messages: Specific error logs (paste directly).
  • Reproduction: Specific steps to reproduce the error (required).

Phase 2: Isolation & Hypothesis (Isolation & Hypothesis)

  • Create file .agent/debug/[issue-slug].md to save the investigation log.
  • Hypotheses: "Maybe the error lies in function X because of Y".
  • Use the commands grep , log to verify the hypothesis.

Phase 3: Root Cause Found (Determine the cause)

  • Only end the investigation when the specific line of code/configuration causing the error is found.
  • Explain WHY it fails instead of just saying IT IS ERROR.

Phase 4: Fix Proposal (Proposal to fix errors)

  • Do not correct errors directly in this skill.
  • The output is either a proposed fix or the creation of a gap_plan for speckit.implement to execute.

🚫 Guard Rails

  • NO guessing. Every conclusion must have evidence from logs or code.
  • DO NOT further damage existing code during debugging (use Read-only tools mainly).
  • MUST create a debug log file to save traces.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most debug triage skills give in 325 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • Investigate root cause before proposing any fixin 102 of 839, across 67 files
  • Read error messages completelyin 89 of 839, across 49 files
  • Create a failing test case before fixingin 84 of 839, across 46 files
  • Reproduce the issue consistentlyin 82 of 839, across 41 files
  • Change one variable at a timein 82 of 839, across 42 files
  • Check recent changesin 74 of 839, across 36 files
  • Write the regression test before fixingin 74 of 839, across 40 files
  • Fix the root cause not the symptomin 60 of 839, across 45 files
  • Implement a single fix at a timein 59 of 839, across 20 files
  • Trace data flow backward to the sourcein 50 of 839, across 20 files
  • Remove all debug instrumentationin 49 of 839, across 13 files
  • Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

  • document the expected behavior
  • paste specific error logs directly
  • define specific steps to reproduce the error
  • formulate hypotheses for the error
  • verify hypotheses using logs and code search
  • explain why the code fails

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.