testing-vlsi-verify-agentic

Test the VLSI agentic verification pipeline end-to-end with deterministic and OpenAI-backed runs.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/ProgMastermind/vlsi-verify-agentic --skill testing-vlsi-verify-agentic-progmastermind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-vlsi-verify-agentic
Source: https://github.com/ProgMastermind/vlsi-verify-agentic/tree/main/.agents/skills/testing-vlsi-verify-agentic
Command: npx skills add https://github.com/ProgMastermind/vlsi-verify-agentic --skill testing-vlsi-verify-agentic-progmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying changes to a multi-agent hardware verification pipeline requires repeatable end-to-end checks across orchestrators, agents, schemas, simulator fallbacks, and coverage extraction, which is error-prone to do manually. ## Core Features & Use Cases - Deterministic End-to-End Testing: Run the APB example pipeline and assert workspace artifacts such as run_state.json, closure_decisions.json, and signoff_package.md. - Simulator-Derived Coverage Validation: Verify Icarus-based functional coverage harness output (FCOV_BIN lines, coverage JSON) for the devin_pipeline_controller and uart_lite demos. - OpenAI-Backed Audit Testing: Validate LLM call logs, agent introspection reports, and artifact audits when OPENAI_API_KEY is configured. - Use Case: After modifying Agent 6's coverage extraction logic, run the fcov-test demo and confirm coverage_history equals [83.33, 91.67] with coverage_source set to simulator_functional_coverage_stdout. ## Quick Start Ask the agent to run the deterministic APB end-to-end test with a fresh run id and verify the workspace artifact assertions.

Frequently Asked Questions about testing-vlsi-verify-agentic

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

FAQPage Schema
How do I test the VLSI agentic verification pipeline end-to-end?▼

Run python run.py with the APB example spec and DUT using a fresh run id, then assert workspace artifacts like run_state.json phase TERMINATE and closure_decisions.json halt_reason closure. The skill lists exact expected values for each artifact.

How do I verify functional coverage extraction from the Icarus simulator?▼

Run examples/devin_pipeline_demo/run_demo.sh with a fresh run id and check sim/iteration_*_functional_coverage.log for FCOV_BIN lines and the JSON files for coverage_source simulator_functional_coverage_stdout. Expected coverage is 83.33 then 91.67 percent.

Does the pipeline test require an OpenAI API key?▼

No, deterministic local runs need no secrets. OPENAI_API_KEY is only required for OpenAI-backed demo scripts like run_demo_llm.sh, which make real OpenAI-compatible calls and log token usage to reports/llm_calls.jsonl.

What simulators are needed for real HDL evidence?▼

Icarus Verilog (iverilog/vvp) and Verilator are used for RTL smoke tests, lint, and the functional coverage harness. If unavailable, Agent 6 may take a simulator-unavailable fallback path, which should be reported explicitly.

Why can't Verilator or Icarus run the UVM coverage code?▼

Verilator 4.038 and Icarus 11.0 cannot compile SystemVerilog covergroup or uvm_pkg. The pipeline emits UVM-style coverage as an artifact but uses a plain Verilog FCOV_BIN display protocol parsed by Agent 6; full UVM coverage needs VCS, Xcelium, or Questa.