debug-coffee-ahk

Debug coffee-ahk compilation by running the full debug workflow with node -e "import('./dist/index.js').then(m=>m.default('file.coffee', {verbose:true, ast:true}))". This exposes the three-stage pipeline—Formatters, Processors, Renderer—so you can pinpoint rendering errors, token omissions, and execution order issues.

The coffee-ahk compiler uses a three-stage pipeline: Formatters (initial input processing), Processors (scope transforms and token manipulation), and Renderer (final AHK output generation). Understanding this flow helps you isolate bugs at each phase and trace token flow from entry/index.ts through to output.

Run debug commands with the verbose and ast flags to inspect Abstract Syntax Trees and token output. Use Read/Grep/Glob for path-based context to document file responsibilities, then validate fixes via the provided debug commands and test workflow.

Yes. The coffee-ahk compiler converts CoffeeScript files to AutoHotkey output. This Skill helps you debug compilation issues when the output is incorrect or incomplete, using inspection tools and a methodical three-stage debugging approach.

Inspect the AST and tokens at each stage—Formatters, Processors, Renderer—to locate where tokens are omitted or incorrectly rendered. Use the debug workflow to trace execution order, then validate your fix by recompiling and comparing the output.