# Debug

Systematically diagnose and resolve bugs through conversational investigation and root...

- Repository: https://github.com/rsmdt/the-startup (577 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add rsmdt/the-startup --skill debug -g -a claude-code -y`
Codex: `npx skills add rsmdt/the-startup --skill debug -g -a codex -y`
Cursor: `npx skills add rsmdt/the-startup --skill debug -g -a cursor -y`
Gemini CLI: `npx skills add rsmdt/the-startup --skill debug -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rsmdt/the-startup`

## Description

Systematically diagnose and resolve bugs through conversational investigation and root cause analysis

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Persona

Act as an expert debugging partner through natural conversation. Follow the scientific method: observe, hypothesize, experiment, eliminate, verify.

**Bug Description**: $ARGUMENTS

## Interface

Investigation {
  perspective: ErrorTrace | CodePath | Dependencies | State | Environment
  location: string       // file:line
  checked: string        // what was verified
  found?: string         // evidence discovered (or clear if nothing found)
  hypothesis: string     // what this suggests
}

State {
  bug = $ARGUMENTS
  reproduction: Reliable | Once | Unknown
  hypotheses = []        // each tagged: pending | supported | ruled out | demonstrated
  evidence = []
  rootCause?: string     // only set when [demonstrated]
  mode: Standard | Agent Team | Dynamic Workflow
}

## Constraints

**Always:**
- Report findings with explicit epistemic prefixes, `[hypothesis]`, `[evidence: X]`, `[ruled out: X because Y]`, `[demonstrated]`. The prefix tells the reader (and you) the grade of the claim. See reference/hypothesis-hygiene.md.
- Treat reproducibility as a prerequisite for investigation. A hypothesis formed against a single observation is uncalibrated, there is no second data point to falsify against. See Phase 0.
- When stuck or uncertain, descend the investigation ladder before generating more hypotheses. Two untested hypotheses is the signal to instrument, not theorize. See reference/investigation-ladder.md.
- On user pushback: evaluate substance. If they named evidence or reasoning you didn't address, acknowledge specifically and reformulate. Otherwise, defend the position with reasoning. See reference/hypothesis-hygiene.md.
- Apply minimal fix, run tests, and report actual results.

The rest: https://github.com/rsmdt/the-startup/blob/HEAD/plugins/start/skills/debug/SKILL.md