agentsclimarketplace

Debug

Skill bromso/metapowers/plugins/development/skills/debug

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill 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

  • 1 stars1 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

Investigate root causes systematically using scientific method

SKILL.md

2.0 KB, 478 tokens by cl100k_base, as published. Nobody here has run it

Debug

Investigate and fix the issue described in "$ARGUMENTS" using systematic root cause analysis. No guessing — find the cause before attempting fixes.

Prerequisites

None — this is a utility skill that can run anytime a bug is encountered.

Process

Phase 1: Investigation

  1. Read error messages carefully:

    • Read the full error output, stack trace, and any warnings
    • Note file paths, line numbers, and error codes
    • Don't skip past errors — they often contain the solution

  2. Reproduce the issue:

    • Identify the exact steps to trigger the bug
    • Can it be triggered reliably?
    • If not reproducible, gather more data before proceeding

  3. Check recent changes:

    • What changed recently that could cause this? (git log, git diff)
    • New dependencies, config changes, environment differences?

Phase 2: Analysis

  1. Trace the data flow:

    • Where does the bad value originate?
    • Trace backward through the call stack to the source
    • Fix at the source, not at the symptom

  2. Find working examples:

    • Is there similar code that works correctly?
    • What's different between working and broken?

Phase 3: Hypothesis

  1. Form a single hypothesis:

    • State clearly: "I think X is the root cause because Y"
    • Be specific, not vague

  2. Test minimally:

    • Make the smallest possible change to test the hypothesis
    • One variable at a time
    • If it doesn't work, form a NEW hypothesis — don't pile fixes

Phase 4: Fix

  1. Write a failing test that reproduces the bug

  2. Implement the fix — address the root cause, not the symptom

  3. Verify:

    • The failing test now passes
    • No other tests broke
    • The original issue is resolved

  4. Commit the fix with a clear message explaining what was wrong and why

Output

Present findings to the user:

  • What the root cause was
  • What was changed to fix it
  • The commit hash
  • Any related issues discovered during investigation

What ships with it

Read from the repository

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

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.