lowdefy

L Debug Trace — Testing skill for Claude Code

Testing community

Analytically debug issues by tracing data flow through code - no logs, no test-and-see.

How to install L Debug Trace

Installs to ~/.claude/commands/lowdefy-lowdefy-l-debug-trace.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/lowdefy/lowdefy/HEAD/.claude/commands/l-debug-trace.md -o ~/.claude/commands/lowdefy-lowdefy-l-debug-trace.md

Restart Claude Code, or start a new session, for it to be picked up.

What L Debug Trace does


description: Analytically debug issues by tracing data flow through code - no logs, no test-and-see argument-hint: ''

Analytical Debug Trace

Debug issues through pure code analysis and end-to-end reasoning. Trace data flow from entry point to observed symptom, identify where expected and actual behavior diverge, and fix at the source.

Core Philosophy

**You do not debug by running code. You do not add console.log. You do not use trial-and-error.

Alternatives in Testing

  • Debug — You are tasked with helping debug issues during manual testing or implementation 10k ★
  • Skill Debug — Debug issues methodically — use when stuck on errors, test failures, or unexpected behavior 2.8k ★
  • Axiom — Development Changelog — Purpose: Historical record of Axiom development milestones, TDD testing results, and architectural decisions 671 ★

Full documentation available on GitHub

View Source Repository