debug
Hypothesis-driven defect isolation — stack-trace forensics, breakpoint strategy, state inspection, and root-cause confirmation via minimal repro.
Skill by OutlineDriven
Chalk Labs
Need help deploying debug?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/outlinedriven-debug-ca2630
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/debug
What's inside
- Skill name
debug- Description
- Hypothesis-driven defect isolation — stack-trace forensics, breakpoint strategy, state inspection, and root-cause confirmation via minimal repro. Use when a defect surfaces (test failure, crash, exception, wrong output, intermittent flake) and the cause is not immediately obvious from the change set.
- License
- Apache-2.0
- Instructions
- 70 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
A bug is a falsified assumption. Find the assumption, falsify it deliberately, observe the divergence, narrow until one line owns the lie. No speculation, no shotgun edits, no "fix and rerun" guessing. ## When to Apply / NOT Apply: test fails and cause unclear; production stack trace; intermittent / flaky behavior; wrong output without crash; regression after known commit window; heisenbug. NOT apply: performance regression with correct outputs; security defect; symptom obvious from one-line read; architectural confusion. ## Anti-patterns - **Shotgun debugging**: editing several files hoping one fixes it. - **Print-and-rerun**: adding logs without a target observation. - **Premature fix**: patching symptom before isolating root cause. - **Ignoring the trace**: stack frames are evidence. - **Changing two variables at once**: defeats falsification. - **Deleting the failing test**: capturing the bug is the asset. ## Hypothesis Loop (language-neutral) 1. **Observe** — Reproduce the failure deterministically. 2. **Trace** — Read the failure artifact (stack, log, core dump). 3. **Hypothesize** — One falsifiable claim. Rank hypotheses by likelihood. 4. **Instrument** — Insert minimum probe (breakpoint, structured log, assertion). 5. **Run** — Execute the minimal repro. 6. **Confirm or refute** — If refuted, demote and pick next hypothesis. 7. **Narrow** — Binary-search the suspect range. Use `git bisect` for regressions. 8. **Confirm root cause** — Inverse test: removing/altering the cause must restore correctness. 9. **Hand off** — Forward to TDD: minimal repro becomes permanent failing test. ## Stack-Trace Reading - **Top frame is innermost**: the failure point. - **Cause vs context**: An exception's `caused by` chain encodes *why*; the stack encodes *where*. - **Async traces**: virtual stacks drop frames between awaits — capture causal context. - **Symbol fidelity**: Strip-mode binaries lose frame names. Build with debug info. - **Inlined / optimized frames**: `<inlined>` markers signal source-line-to-instruction map is approximate. ## Parallel Tooling | Family | Live debugger | Postmortem / record | Remote attach | |---|---|---|---| | Systems (C/C++/Rust) | `gdb`, `lldb`, `rust-gdb`, `rust-lldb` | `coredumpctl` + `gdb core`, `rr record/replay` | `gdb -p <pid>` / `lldb -p <pid>` | | Python | `pdb`, `ipdb`, `pdbpp`, `breakpoint()` | `faulthandler`, `py-spy dump`, traceback module | `debugpy --listen` | | Go | `dlv debug`, `dlv test`, `dlv attach <pid>` | `runtime/pprof`, GOTRACEBACK=crash | `dlv connect <addr>` | | Java/Kotlin | IntelliJ debugger, `jdb` | hs_err logs, JFR, heap dump (`jmap`) | JDWP `-agentlib:jdwp=...` | | JavaScript/TypeScript | `node --inspect`, Chrome DevTools | `--report-uncaught-exception` reports | `--inspect=0.0.0.0:9229` | | OCaml | `ocamldebug`, `Printexc.record_backtrace true` | core file + `ocaml-gdb`, memtrace | `ocamldebug -s <socket>` | Use `procs` (not `ps`) for PID. Use `bat -P -p -n` (not `cat`) for trace files. Use `git grep -n -C 3 'pattern'` (not `grep`) for callsites. ## Constitutional Rules 1. **Reproduce before fixing**. 2. **One hypothesis at a time**. 3. **Evidence over inference**. 4. **Capture the bug as a test** (hand to TDD). 5. **Confirm with inverse**. 6. **Bisect for regressions**. 7. **No silent edits**. ## Reasoning approach Before hypothesizing a fix, reason through the failure — SHORT-form KEYWORDS for trace notes, observe the symptoms, trace the execution path, break down where actual behavior diverges from expected, critically review each candidate cause, validate each hypothesis against the evidence. The root cause is the smallest explanation that accounts for all observed symptoms. For numeric calculation (timing math, bound arithmetic, off-by-N analysis), invoke `fend` per the baseline rule; never self-calculate. Causal reasoning and trace interpretation are in-head — they are not arithmetic. ## Pre-flight Check - Before writing a plan for a bug fix that touches multiple files - Whenever you notice that the previous attempt to fix a bug failed
From OutlineDriven/odin-codex-plugin, Apache-2.0.
More from OutlineDriven/odin-codex-plugin
- 0.525score
improve-codebase-architecture
OutlineDriven
Surface deepening refactors that turn shallow modules into deep ones, informed by `CONTEXT.md` and `docs/adr/`.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
memory-update
OutlineDriven
Scan agent's session-history transcripts for save-worthy signals (corrections, preferences, decisions, references), propose and write auto-memory files with…
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
fix
OutlineDriven
Polymorphic iterative repair loop — accept a verifier failure, structured findings (review/resolve/triage-issue), or a bug description; modify→verify→keep on…
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
git-branchless
OutlineDriven
Enforce idiomatic git-branchless during planning and executing tasks — detached-HEAD-first work, in-memory rebase via `git move`, event-log recovery via `git…
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
memory-sanitize
OutlineDriven
Produce share-safe copies of memory files under /tmp with PII redacted (paths, emails, session IDs, dates) and credentials scanned (tokens, keys); never…
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
memory-clean
OutlineDriven
Audit memory directory for structural issues (orphans, dangling refs, duplicates, missing sections, oversized entries) and staleness against session-history…
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
cleanup-codebase
OutlineDriven
Reduce concepts, duplication, and ceremony in internal code while touching nearby code.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
domain-model
OutlineDriven
Grill against the existing domain model.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
design
OutlineDriven
Set visual and interaction direction for any UI surface (web, React, TUI, CLI, desktop, Qt, design-system tokens) before any UI code.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
gh-fix-ci
OutlineDriven
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize the failure, then plan and implement the fix after user approval.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
design-by-contract
OutlineDriven
Design-by-Contract (DbC) development.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
proof-driven
OutlineDriven
Proof-driven development.
SkillCFreshness: C★ 14Claude Code +9
Signals
- Stars
- 14
- Forks
- 2
- Open issues
- 2
- Last commit (this folder)
- May 3, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Website
- outlinedriven.github.io
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from OutlineDriven
- 0.525score
design-by-contract
OutlineDriven
Design-by-Contract (DbC) development.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
fix
OutlineDriven
Polymorphic iterative repair loop — accept a verifier failure, structured findings (review/resolve/triage-issue), or a bug description; modify→verify→keep on…
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
cleanup-codebase
OutlineDriven
Reduce concepts, duplication, and ceremony in internal code while touching nearby code.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
design
OutlineDriven
Set visual and interaction direction for any UI surface (web, React, TUI, CLI, desktop, Qt, design-system tokens) before any UI code.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
domain-model
OutlineDriven
Grill against the existing domain model.
SkillCFreshness: C★ 14Claude Code +9 - 0.525score
gh-fix-ci
OutlineDriven
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize the failure, then plan and implement the fix after user approval.
SkillCFreshness: C★ 14Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get debug running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
debug skill. Agent Mart. https://agentmart.dev/skills/outlinedriven-debug-ca2630 (last updated 2026-10-24)