Skip to content
Agentmart
Submit a tool

debugging

When there is a bug, error, failed test, regression, performance drop, unexpected result, or anomalous data, establish a tight feedback loop and find the root…

Skill by DearCaat

IndexedMIT★ 4
Write a review

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/dearcaat-debugging

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.

We use your email only for this newsletter. Privacy

About

When there is a bug, error, failed test, regression, performance drop, unexpected result, or anomalous data, establish a tight feedback loop and find the root cause before fixing. Use executing-plans for normal execution without a fault signal.

Use cases: testing, data

No 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/debugging

What's inside

Skill name
debugging
Description
When there is a bug, error, failed test, regression, performance drop, unexpected result, or anomalous data, establish a tight feedback loop and find the root cause before fixing. Use executing-plans for normal execution without a fault signal.
License
MIT
Instructions
23 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Debugging

Systematic debugging is faster than thrashing.

## Iron law

Do not propose a fix until the root cause has evidence. Treating a symptom as the cause is failure.

## Method

- Build a tight feedback loop first: find a fast, deterministic, repeatable command that makes the issue fail. Once the loop exists, 90% of the problem is solved.
- For nondeterministic issues, increase the reproduction rate enough to investigate instead of demanding a perfectly clean reproduction.
- Unexpected experimental results follow the same rule: reproduce, rule out pipeline errors, attribute with one variable at a time, then discuss scientific explanations.

## Gate

Reproduce → minimize → test single-variable hypotheses → fix → regression-test. First show that the test turns red for this problem, then show that the fix turns it green. If a gate fails, do not advance.

## Completion criterion

The root cause is supported by evidence, the fix makes the loop green, and regression verification is recorded.

From DearCaat/research-foundation-skills, MIT.

More from DearCaat/research-foundation-skills

Signals

Stars
4
Forks
0
Open issues
0
Last commit (this folder)
Sep 2, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from DearCaat

Cite this page

debugging skill. Agent Mart. https://agentmart.dev/skills/dearcaat-debugging (last updated 2026-10-24)