Run the repo's canonical build and test workflows. Use this when validating compiler changes, running one test, running regression, or understanding expected-failure tests. Prefer the existing Makefile and tests/regression.py flows.
Use this skill whenever the user wants to plan a large refactor, migration, or multi-step code change that will be executed across multiple agent sessions with fresh context. Triggers include "plan this in phases", "create a phase plan", "break this into…
Triage a failing or misbehaving compiler test. Use this at the start of any debug session when a test is failing, a signal has a wrong value, a simulation mismatch appears, or a pass starts regressing and you need to choose the right artifact and workflow…
Inspect DFG .json or .dot debug artifacts produced by the compiler. Use this when debugging signal drivers, dependencies, fanout, op behavior, pass-to-pass changes, dead code, or node identity questions. Prefer tools/dfg_inspect.py and correlate with runtime…
Inspect VCD files from custom-sim or Verilator. Use this when debugging waveform values, transitions, or mismatches. Prefer tools/vcd_inspect.py and the unified tools/vcd_diff.py.
Trace runtime DFG evaluation in custom simulation. Use this when static DFG artifacts are not enough and you need to observe how specific nodes, cones, or operation classes evaluated over time, including operation-specific decisions emitted into…
Scaffold a new compiler testcase in tests/. Use this when creating new test scaffolding from scratch. For RTL and TB coding rules, see testcase-rules.
RTL and TB coding rules for compiler testcases. Use this when writing, modifying, or reviewing RTL or a testbench in any test under tests/ — including deciding whether a handwritten TB is needed and validating that it follows the repo's driving rules.