agentsclimarketplace

Debug systematic

Skill manastalukdar/ai-devstudio/skills/debug-systematic

Professional development studio for Claude Code CLI

Install
npx -y skills add manastalukdar/ai-devstudio --skill debug-systematic

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

Systematic debugging workflow with hypothesis testing

SKILL.md

0.7 KB, 127 tokens by cl100k_base, as published. Nobody here has run it

Systematic Debugging Workflow

I'll help you debug issues systematically using the scientific method - hypothesis formation, testing, and iterative refinement.

Arguments: $ARGUMENTS - error description, reproduction steps, or context

Token Optimization

Expected range: 1,500–3,000 tokens (initial), 400 tokens (cache hit)

Caching: Caches debug state in .claude/cache/debug/ for 7 days.

Early exit: Returns immediately if error pattern matches a known cached solution.

Patterns used: Grep-before-Read, early exit, caching, progressive disclosure

What ships with it

Read from the repository

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

Gives 1 of the 12 instructions most debug triage skills give in 127 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • Investigate root cause before proposing any fixin 102 of 839, across 67 files
  • Read error messages completelyin 89 of 839, across 49 files
  • Create a failing test case before fixingin 84 of 839, across 46 files
  • Reproduce the issue consistentlyin 82 of 839, across 41 files
  • Change one variable at a timein 82 of 839, across 42 files
  • Check recent changesin 74 of 839, across 36 files
  • Write the regression test before fixingin 74 of 839, across 40 files
  • Fix the root cause not the symptomin 60 of 839, across 45 files
  • Implement a single fix at a timein 59 of 839, across 20 files
  • Trace data flow backward to the sourcein 50 of 839, across 20 files
  • Remove all debug instrumentationin 49 of 839, across 13 files
  • Form a single hypothesishere, and in 48 of 839, across 18 files

Said here and by no other author read

  • refine the hypothesis iteratively
  • cache debug state for seven days
  • return immediately if error pattern matches cache

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.