skills.rest
SergeiGolos
SergeiGolosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

runtime-debugger

Traces output statements, stack levels, lifecycle events in WOD Wiki runtime engine workoutscripts using Node/Bun environment for JIT compilation inspection.

1|Updated Dec 21, 2024
Search Tags:#typescript#debugging#runtime#trace#workout#script execution
One-click install
npx skills add https://github.com/SergeiGolos/wod-wiki --skill runtime-debugger-sergeigolos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runtime-debugger
Source: https://github.com/SergeiGolos/wod-wiki/tree/main/.gemini/skills/runtime-debugger
Command: npx skills add https://github.com/SergeiGolos/wod-wiki --skill runtime-debugger-sergeigolos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and fix unexpected behavior in the WOD Wiki runtime engine, ensuring workout scripts execute as intended.

Core Features & Use Cases

  • Detailed Tracing: Provides deep visibility into workout script execution, including system outputs, segment timings, and stack transitions.
  • Controlled Environment: Runs scripts in a Node/Bun environment for safe and thorough inspection without affecting the live application.
  • Use Case: If a workout's timing is off or certain exercises aren't completing correctly, use this Skill to trace the execution flow and pinpoint the exact cause of the error.

Quick Start

Use the runtime-debugger skill to trace the execution of the script '30 Clean & Jerk 135lb'.

Frequently Asked Questions about runtime-debugger

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

FAQPage Schema
How do I trace workout script execution to debug missing outputs?▼

Trace workout script execution by monitoring system outputs, segment timings, and stack transitions to pinpoint where runtime behavior deviates from expected results and identify missing output sources.

Why does my workout script timing appear incorrect during execution?▼

Workout script timing issues stem from unexpected stack transitions or execution flow deviations. Tracing stack levels and lifecycle events isolates the exact execution step causing timing discrepancies.

Do I need a Node or Bun environment to debug workout runtime behavior?▼

A controlled Node or Bun environment is required for deep inspection of JIT compilation and execution strategies when debugging the workout runtime engine to ensure safe, thorough script analysis.

What is the best way to inspect stack transitions in TypeScript workout scripts?▼

Inspecting stack transitions requires tracing lifecycle events and output statements within a controlled runtime environment, providing deep visibility into how stack levels shift during workout script execution.

Can I use this debugger on a live application to trace runtime errors?▼

Runtime debugging must run in a controlled Node or Bun environment for safe, thorough inspection without affecting the live application, ensuring workout script execution analysis remains isolated.

When should I trace lifecycle events for workout script debugging?▼

Trace lifecycle events when runtime behavior is unexpected, outputs are missing, or stack transitions require verification to accurately diagnose workout script execution flow and identify error causes.

Related Skills

Explore More Software Engineering Skills→
samymitysamymity
1

bun-runtime

Migrate Node commands and npm scripts to Bun equivalents.

Community
Intermediate
iciakkyiciakky

debug

Diagnoses root causes of code modifications using a seven-step debugging workflow and generates verified fix plans.

Community
Intermediate
nlelouchenlelouche
71

menu-navigation-flow

Implement stack-based UI navigation with push, pop, and modal operations in Unity UI Toolkit.

Community
Intermediate
backengineeringbackengineering
434

dynamic-instrumentation

Instrument binaries and trace runtime behavior using LLVM infrastructure.

Official
Advanced