Debug Workflow

The Debug Workflow skill provides developers with a structured, interactive approach to diagnosing and resolving failing scenario tests within the picotorokko ecosystem. Designed for Ruby developers, this skill centers on the Ruby debug gem, facilitating precise control over code execution, variable inspection, and environmental state verification. It is essential for developers working on complex CLI workflows, build system tasks, or mrbgem development who need to understand exactly how their code interacts with the underlying file system and shell environment.

• Precise step-by-step execution control using commands like step, next, and continue to trace logic flow.

• Interactive variable inspection through pp (pretty-print) and info locals to monitor execution context.

• File system state verification by executing system() commands directly within the debug session to inspect temporary build directories or artifacts.

• Pattern-based debugging strategies for common test failure scenarios, such as command success validation, assertion matching, and multi-step workflow tracing.

• Integration with project-specific test helpers, such as generate_project_id and run_ptrk_command, to simulate and observe real-world execution environments.

• Ideal for TDD cycles where immediate feedback on test failures is required.

• Provides guidance on interpreting Process::Status objects and shell execution outputs.

• Helps identify mismatches between expected file system states and actual outcomes created by CLI commands.

• Simplifies the process of setting up isolated debugging sessions for specific test files using ruby -r debug -Itest flags.

• Acts as a bridge between high-level architectural design and low-level code issues, allowing developers to dive into the call stack of failing assertions to pinpoint the exact line of failure.