step-through-code

Step through Node.js and browser code execution paths in a tmux debugger.

Updated Oct 15, 2021
One-click install
npx skills add https://github.com/toqoz/config --skill step-through-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: step-through-code
Source: https://github.com/toqoz/config/tree/main/home/agents/skills/step-through-code
Command: npx skills add https://github.com/toqoz/config --skill step-through-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ws, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the gap between writing code and verifying its runtime behavior, allowing you to catch logic errors, async issues, and side-effect bugs before they manifest in production.

Core Features & Use Cases

  • Real-time Debugging: Step through execution line-by-line using Node.js or Chrome DevTools Protocol (CDP) to inspect variable states and control flow.
  • Verification Envelope: Provides a structured, disciplined approach to verify high-risk code paths like complex branching, async boundaries, and side effects.
  • Use Case: When implementing a complex API route handler or a critical state transition in a React component, use this skill to confirm that every variable and branch behaves exactly as expected during execution.

Quick Start

Use the step-through-code skill to verify the execution flow of the new authentication module by setting up a two-pane tmux session and stepping through the target function.

Frequently Asked Questions about step-through-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify runtime correctness by stepping through Node.js or browser code?

You can verify runtime correctness by setting up a two-pane tmux session and using Node.js or Chrome DevTools Protocol (CDP) to step through execution line-by-line, inspecting variable states and control flow.

What is the best way to debug complex branching and side effects in server-side API handlers?

The best way to debug complex branching and side effects in API handlers is using a structured verification envelope to step through execution paths, inspecting internal state and observable outcomes against a deterministic trigger command.

Do I need a tmux environment to inspect variable states during real-time debugging?

Yes, you need a tmux environment to inspect variable states during real-time debugging, as the skill requires tmux to manage the two-pane session for stepping through the target function execution.

Can I use Chrome DevTools Protocol to step through client-side browser logic with async boundaries?

Yes, you can use Chrome DevTools Protocol (CDP) to step through client-side browser logic, inspecting variable states and control flow to verify high-risk code paths like async boundaries and complex state transitions.

Why should I use a deterministic trigger command when verifying code logic in a debugger?

A deterministic trigger command is required to reliably reproduce the execution path, allowing the debugger to inspect the exact internal state and verify observable outcomes consistently across multiple debugging sessions.

What are the limitations of using step-through-code verification for state transitions?

Limitations include requiring a deterministic trigger command and a tmux environment, meaning non-deterministic or hard-to-reproduce state transitions without a clear trigger command cannot be effectively verified.