bb-trace-signal-path

Trace signal paths through AST JSON from source to sink.

41|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/amoslee2026/Babel --skill bb-trace-signal-path
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-trace-signal-path
Source: https://github.com/amoslee2026/Babel/tree/main/.claude/skills/bb-trace-signal-path
Command: npx skills add https://github.com/amoslee2026/Babel --skill bb-trace-signal-path

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Trace signal paths through AST JSON to identify source-to-sink propagation and cross-clock-domain transitions. This helps root-cause CDC violations and optimize timing analysis across modules.

Core Features & Use Cases

  • DFS-based signal path tracing across module hierarchy from source to sink in the AST JSON.
  • Outputs path details, cross_clock_domain flag, and script-assisted verification artifacts.
  • Use Case: CDC root-cause analysis when a violation is reported by bb-check-cdc or for critical path debugging.

Quick Start

Trace the signal path from the designated source to the sink in the AST to identify CDC crossing and generate a trace report.

Frequently Asked Questions about bb-trace-signal-path

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

FAQPage Schema
How do I trace cross-clock-domain signal paths for CDC root-cause analysis?

Trace cross-clock-domain signal paths by executing DFS traversal across module hierarchies in AST JSON from source to sink. It outputs a structured JSON trace detailing propagation paths and flagging cross-clock-domain transitions for CDC debugging.

What is the best way to debug critical signal paths across multi-module HDL designs?

Debug critical signal paths by tracing source-to-sink propagation through AST JSON across multi-module HDL designs. This identifies cross-clock-domain transitions and generates script-assisted verification artifacts for timing analysis.

How do I start signal tracing from a source to a sink in AST JSON?

Start signal tracing by providing the source_signal, sink_signal, and design_name arguments to the parsing scripts. The tool traverses the AST JSON to output structured path details and Python scripts for rendering verification artifacts.

Does CDC signal tracing require a specific AST JSON format as input?

CDC signal tracing requires AST JSON produced by bb-parse-ast as input. It consumes this specific format to traverse module hierarchies and identify cross-clock-domain transitions during path tracing.

Can I use this for CDC analysis after a violation is reported by bb-check-cdc?

Use it for CDC root-cause analysis after a violation is reported by bb-check-cdc. It traces the exact signal path through AST JSON from source to sink to pinpoint the cross-clock-domain transition.