Skip to content
Engineering

Systematic Debugging

obra/superpowers

Trace a failure through callers and evidence before changing code; test the smallest explanation.

SKILL.md

---
name: knoveya-systematic-debugging
description: "Trace a failure through callers and evidence before changing code; test the smallest explanation. Use for matching engineering work."
---

# Systematic Debugging

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Trace a failure through callers and evidence before changing code; test the smallest explanation.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

The proposed fix addresses the cause and reproducer, not only one symptom.

## Example task

Follow a stale filter value from URL parsing to rendered results.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-systematic-debugging as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-systematic-debugging/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Follow a stale filter value from URL parsing to rendered results.

Verify

The proposed fix addresses the cause and reproducer, not only one symptom.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.