simulate

Automates Verilator simulation runs and structured pass/fail reporting from logs.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xsw632/ChipAgent --skill simulate-xsw632
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simulate
Source: https://github.com/xsw632/ChipAgent/tree/main/skills/simulate
Command: npx skills add https://github.com/xsw632/ChipAgent --skill simulate-xsw632

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires verilator, and includes scripts (resource) components.

What problem does it solve?

Manually running Verilator simulations, parsing log files, and tracking test results for hardware modules is tedious and error-prone, especially during iterative hardware design cycles.

Core Features & Use Cases

  • Prerequisite Validation: Automatically checks that generated Verilog and C++ testbench files exist for the target module before running simulation, preventing wasted execution time on incomplete workflows.
  • Standardized Execution: Runs the project's pre-configured simulate.sh wrapper script to ensure consistent simulation settings and environment across all hardware modules.
  • Structured Result Reporting: Parses simulation logs to generate clear pass/fail summaries with per-test breakdowns, and provides targeted troubleshooting suggestions if simulations fail.
  • Use Case: For example, after generating Verilog and a testbench for a 4-bit ALU, use this skill to instantly run all test cases and identify any failing operations without manual command execution or log parsing.

Quick Start

Use the simulate skill to run a Verilator simulation for your 4-bit ALU module and get a complete summary of all test results.

Frequently Asked Questions about simulate

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

FAQPage Schema
How do I automate Verilator simulation execution for RTL verification?

To automate Verilator simulation execution for RTL verification, you can use a wrapper script that handles testbench execution and log parsing automatically. This eliminates manual command running and delivers structured pass/fail summaries for hardware modules like ALUs and counters.

What files are required before running a Verilator hardware simulation?

Before running a Verilator hardware simulation, you need generated Verilog files and C++ testbench files for the target module. Prerequisite checks ensure these files exist to prevent wasted execution time on incomplete workflows.

How does parsing simulation logs help with hardware design troubleshooting?

Parsing simulation logs helps with hardware design troubleshooting by generating structured pass/fail summaries with per-test breakdowns. When simulations fail, parsed logs provide targeted troubleshooting suggestions to identify failing operations without manual analysis.

Can I run Verilator simulations for custom logic modules with a standardized script?

Yes, you can run Verilator simulations for custom logic modules using a pre-configured simulate.sh wrapper script. This ensures consistent simulation settings and environment across all hardware modules during iterative design cycles.

Why does my Verilator testbench simulation fail to execute properly?

Verilator testbench simulation execution fails when prerequisite generated Verilog or C++ testbench files are missing. The automated prerequisite validation checks for these files before running simulation to prevent wasted execution time on incomplete workflows.

What is the best way to validate generated Verilog against a testbench?

The best way to validate generated Verilog against a testbench is running an automated Verilator simulation that executes all test cases instantly. This provides a complete summary of test results and identifies any failing operations without manual command execution.