CtrlK
BlogDocsLog inGet started
Tessl Logo

jbvc/systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

61

Quality

61%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

test-academic.md

Academic Test: Systematic Debugging Skill

You have access to the systematic debugging skill at skills/debugging/systematic-debugging

Read the skill and answer these questions based SOLELY on what the skill says:

  1. What are the four phases of systematic debugging?
  2. What must you do BEFORE attempting any fix?
  3. In Phase 3, what should you do if your first hypothesis doesn't work?
  4. What does the skill say about fixing multiple things at once?
  5. What should you do if you don't fully understand the issue?
  6. Is it ever acceptable to skip the process for simple bugs?

Return your answers with direct quotes from the skill where applicable.

condition-based-waiting.md

CREATION-LOG.md

defense-in-depth.md

find-polluter.sh

root-cause-tracing.md

SKILL.md

test-academic.md

test-pressure-1.md

test-pressure-2.md

test-pressure-3.md

tile.json