Skip to content

Eriemon/verilog-generator

readable-verilog-generator

Verified

Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed repair, and workflow trace diagnosis.

FileKindSize
SKILL.mdskill md21.3 KB
agents/openai.yamlconfig363 B
assets/examples/existing_rtl/fsm_without_default.vother761 B
assets/examples/existing_rtl/fsm_without_default_spec.mdmarkdown311 B
assets/examples/existing_rtl/leaf_counter.vother314 B
assets/examples/existing_rtl/missing_output_register.vother423 B
assets/examples/existing_rtl/missing_output_register_spec.mdmarkdown331 B
assets/examples/existing_rtl/ready_valid_slice.vother967 B
assets/examples/existing_rtl/ready_valid_slice_spec.mdmarkdown420 B
assets/examples/existing_rtl/reset_gap_counter.vother319 B
assets/examples/existing_rtl/reset_gap_counter_spec.mdmarkdown212 B
assets/examples/existing_rtl/tb_ready_valid_slice.vother846 B
assets/examples/existing_rtl/top_counter.vother271 B
assets/examples/existing_rtl/traffic_light.vother2.5 KB
assets/examples/existing_rtl/traffic_light_spec.mdmarkdown585 B
assets/examples/readme/axis_packet_meter.vother10.2 KB
assets/examples/remote_fixtures/comb_hierarchy_budget/generated/rtl/comb_hierarchy_budget.vother1.9 KB
assets/examples/remote_fixtures/comb_hierarchy_budget/generated/tb/tb_comb_hierarchy_budget.vother2.5 KB
assets/examples/remote_fixtures/comb_hierarchy_budget/hierarchy_child_loop.vother447 B
assets/examples/remote_fixtures/comb_hierarchy_budget/hierarchy_over_budget.vother527 B
assets/examples/remote_fixtures/comb_hierarchy_budget/hierarchy_q_cut.vother467 B
assets/examples/remote_fixtures/comb_hierarchy_budget/hierarchy_within_budget.vother450 B
assets/examples/remote_fixtures/comb_hierarchy_budget/spec.jsonconfig1.7 KB
assets/examples/remote_fixtures/comb_operation_budget/comb_operation_budget_bad.vother187 B
assets/examples/remote_fixtures/comb_operation_budget/generated/rtl/comb_operation_budget.vother6.1 KB
assets/examples/remote_fixtures/comb_operation_budget/generated/tb/tb_comb_operation_budget.vother5.7 KB
assets/examples/remote_fixtures/comb_operation_budget/spec.jsonconfig2.9 KB
assets/examples/remote_fixtures/comb_parity_mux/generated/rtl/comb_parity_mux.vother2.1 KB
assets/examples/remote_fixtures/comb_parity_mux/generated/tb/tb_comb_parity_mux.vother2.8 KB
assets/examples/remote_fixtures/comb_parity_mux/spec.jsonconfig1.9 KB
assets/examples/remote_fixtures/pipeline_delay/generated/rtl/pipeline_delay.vother4.5 KB
assets/examples/remote_fixtures/pipeline_delay/generated/tb/tb_pipeline_delay.vother2.6 KB
assets/examples/remote_fixtures/pipeline_delay/spec.jsonconfig2.2 KB
assets/examples/remote_fixtures/ready_valid_slice/generated/rtl/ready_valid_slice.vother5.2 KB
assets/examples/remote_fixtures/ready_valid_slice/generated/tb/tb_ready_valid_slice.vother2.9 KB
assets/examples/remote_fixtures/ready_valid_slice/spec.jsonconfig2.6 KB
assets/examples/rtl_erie_verilog_spec.jsonconfig2.1 KB
assets/examples/use_case_templates/jesd_adc.jsonconfig2.4 KB
assets/examples/use_case_templates/jesd_dac.jsonconfig2.5 KB
assets/examples/use_case_templates/mxfe_mixed.jsonconfig2.7 KB
assets/examples/use_case_templates/spi_adc.jsonconfig2.8 KB
assets/examples/use_case_templates/spi_dac.jsonconfig2.7 KB
assets/examples/verilog_pattern_templates/axi4_lite_csr.jsonconfig2.1 KB
assets/examples/verilog_pattern_templates/axi_interconnect_dma.jsonconfig2.3 KB
assets/examples/verilog_pattern_templates/axis_ready_valid.jsonconfig2.3 KB
assets/examples/verilog_pattern_templates/conv_load_store.jsonconfig1.8 KB
assets/external_interface_catalog.jsonconfig2.9 KB
assets/ideal_bad_style_metrics.jsonconfig17.5 KB
assets/installer/manifest.projection.jsonconfig2.8 KB
assets/installer/platforms.jsonconfig1.3 KB
assets/interface_templates/ahb_lite_config.vincother2.3 KB
assets/interface_templates/apb_config.vincother861 B
assets/interface_templates/axi4_full_master.vincother1.8 KB
assets/interface_templates/axi4_full_slave.vincother1.8 KB
assets/interface_templates/axi4_lite_config.vincother1.6 KB
assets/interface_templates/axi_stream_duplex.vincother1.1 KB
assets/interface_templates/catalog.jsonconfig2.6 KB
assets/project_ip_interface_manifest.template.jsonconfig9.4 KB
assets/readme-workflow.pngbinary1.4 MB
assets/readme/design-profile-cn.pngbinary1.4 MB
assets/readme/design-profile.pngbinary1.4 MB
assets/readme/evidence-guard-cn.pngbinary1.4 MB
assets/readme/evidence-guard.pngbinary1.4 MB
assets/readme/hero-overview-cn.pngbinary1.5 MB
assets/readme/hero-overview.pngbinary1.5 MB
assets/readme/project-facts-cn.pngbinary1.2 MB
assets/readme/project-facts.pngbinary1.3 MB
assets/readme/rule-rendering-cn.pngbinary1.4 MB
assets/readme/rule-rendering.pngbinary1.2 MB
assets/style_templates/header_prompt_none_mode.txtmarkdown2.1 KB
assets/style_templates/header_prompt_table_mode.txtmarkdown2.5 KB
assets/style_templates/rtl_bus_grouping.tplother1.0 KB
assets/style_templates/rtl_fsm.tplother832 B
assets/style_templates/rtl_header_bilingual.tplother1.6 KB
assets/style_templates/rtl_instantiation.tplother496 B
assets/style_templates/rtl_region_order.tplother987 B
assets/use_case_templates/catalog.jsonconfig2.8 KB
assets/use_case_templates/jesd_adc/README.mdmarkdown699 B
assets/use_case_templates/jesd_adc/constraints/system_constr.xdcother454 B
assets/use_case_templates/jesd_adc/manifest.jsonconfig1.7 KB
assets/use_case_templates/jesd_adc/tcl/common_bd.tclother4.0 KB
assets/use_case_templates/jesd_adc/tcl/system_bd.tclother920 B
assets/use_case_templates/jesd_adc/tcl/system_project.tclother1.0 KB
assets/use_case_templates/jesd_adc/verilog/system_top.vother2.9 KB
assets/use_case_templates/jesd_dac/README.mdmarkdown745 B
assets/use_case_templates/jesd_dac/constraints/system_constr.xdcother299 B
assets/use_case_templates/jesd_dac/manifest.jsonconfig1.7 KB
assets/use_case_templates/jesd_dac/tcl/common_bd.tclother4.8 KB
assets/use_case_templates/jesd_dac/tcl/system_bd.tclother923 B
assets/use_case_templates/jesd_dac/tcl/system_project.tclother1.1 KB
assets/use_case_templates/jesd_dac/verilog/system_top.vother2.9 KB
assets/use_case_templates/mxfe_mixed/README.mdmarkdown739 B
assets/use_case_templates/mxfe_mixed/constraints/system_constr.xdcother380 B
assets/use_case_templates/mxfe_mixed/manifest.jsonconfig1.8 KB
assets/use_case_templates/mxfe_mixed/tcl/common_bd.tclother5.4 KB
assets/use_case_templates/mxfe_mixed/tcl/system_bd.tclother1.2 KB
assets/use_case_templates/mxfe_mixed/tcl/system_project.tclother1.2 KB
assets/use_case_templates/mxfe_mixed/verilog/system_top.vother3.4 KB
assets/use_case_templates/spi_adc/README.mdmarkdown925 B
assets/use_case_templates/spi_adc/constraints/system_constr.xdcother635 B
assets/use_case_templates/spi_adc/manifest.jsonconfig1.7 KB
assets/use_case_templates/spi_adc/tcl/common_bd.tclother6.3 KB
assets/use_case_templates/spi_adc/tcl/system_bd.tclother1.6 KB
assets/use_case_templates/spi_adc/tcl/system_project.tclother982 B
assets/use_case_templates/spi_adc/verilog/system_top.vother4.2 KB
assets/use_case_templates/spi_dac/README.mdmarkdown757 B
assets/use_case_templates/spi_dac/constraints/system_constr.xdcother546 B
assets/use_case_templates/spi_dac/manifest.jsonconfig1.6 KB
assets/use_case_templates/spi_dac/tcl/common_bd.tclother5.7 KB
assets/use_case_templates/spi_dac/tcl/system_bd.tclother1.0 KB
assets/use_case_templates/spi_dac/tcl/system_project.tclother981 B
assets/use_case_templates/spi_dac/verilog/system_top.vother3.5 KB
assets/verilog_formatter_config/defaults.jsonconfig6.2 KB
assets/verilog_formatter_config/profiles/conservative.jsonconfig283 B
assets/verilog_formatter_config/profiles/example_compat.jsonconfig484 B
assets/verilog_formatter_config/profiles/formatter-lint.jsonconfig121 B
assets/verilog_formatter_config/profiles/formatter-normalize.jsonconfig182 B
assets/verilog_formatter_config/profiles/formatter-preserve.jsonconfig385 B
assets/verilog_formatter_config/profiles/formatting.jsonconfig270 B
assets/verilog_formatter_config/profiles/lint.jsonconfig269 B
assets/verilog_formatter_config/profiles/migration.jsonconfig239 B
assets/verilog_formatter_config/profiles/stress_cases_compat.jsonconfig484 B
assets/verilog_formatter_config/profiles/vitis-wrapper.jsonconfig486 B
assets/verilog_formatter_config/schema.jsonconfig13.7 KB
assets/verilog_formatter_config/templates/task-batch.jsonconfig212 B
assets/verilog_formatter_config/templates/task-inplace.jsonconfig221 B
assets/verilog_formatter_config/templates/task-single-file.jsonconfig220 B
assets/verilog_pattern_templates/axi4_lite_csr_shell.vincother562 B
assets/verilog_pattern_templates/axi_interconnect_port_groups.vincother592 B
assets/verilog_pattern_templates/axis_ready_valid_slice.vincother494 B
assets/verilog_pattern_templates/catalog.jsonconfig2.2 KB
assets/verilog_pattern_templates/conv_load_store_pipeline.vincother457 B
assets/verilog_pattern_templates/counter_state_bridge.vincother443 B
assets/verilog_pattern_templates/equivalence_wrapper_probe.vincother306 B
assets/verilog_pattern_templates/fsm_state_transition.vincother1.0 KB
assets/verilog_pattern_templates/phase_output_registering.vincother404 B
assets/verilog_pattern_templates/wrapper_top_stitching.vincother608 B
assets/verilog_quality_gates.jsonconfig38.2 KB
assets/verilog_style_rules.jsonconfig11.8 KB
assets/xilinx_primitive_semantics.jsonconfig21.4 KB
references/checklists/capability-distillation-checklist.mdmarkdown3.0 KB
references/checklists/lint-checklist.mdmarkdown3.6 KB
references/checklists/verilog-readability-gate.mdmarkdown3.5 KB
references/corpus/verilog-style-observations.mdmarkdown4.6 KB
references/integration/configuration.mdmarkdown19.9 KB
references/integration/host-integration.mdmarkdown10.6 KB
references/rules/asic-verilog-quality.mdmarkdown3.9 KB
references/rules/erie-style.mdmarkdown6.3 KB
references/rules/testbench-patterns.mdmarkdown3.2 KB
references/rules/verilog-code-comment-naming-standard.mdmarkdown55.6 KB
references/rules/verilog-comment-placement.mdmarkdown8.4 KB
references/rules/verilog-pattern-templates.mdmarkdown1.1 KB
references/rules/verilog-quality-gates.mdmarkdown21.4 KB
references/rules/xilinx-primitive-exemptions.mdmarkdown10.6 KB
references/skill/installation.mdmarkdown6.1 KB
references/skill/script-guide.mdmarkdown7.5 KB
references/skill/skill-standards.mdmarkdown2.1 KB
references/workflows/verilog_dispatcher.mdmarkdown6.4 KB
references/workflows/workflow-contracts.mdmarkdown15.1 KB
scripts/__init__.pyscript53 B
scripts/python/__init__.pyscript55 B
scripts/python/corpus/analyze_verilog_style_corpus.pyscript25.3 KB
scripts/python/existing_rtl/existing_rtl.pyscript81.1 KB
scripts/python/existing_rtl/existing_rtl_improvement.pyscript109.9 KB
scripts/python/existing_rtl/intervention.pyscript8.3 KB
scripts/python/existing_rtl/optimizer.pyscript25.8 KB
scripts/python/existing_rtl/reflection.pyscript86.7 KB
scripts/python/existing_rtl/semantic_contract.pyscript45.6 KB
scripts/python/existing_rtl/verifier.pyscript15.3 KB
scripts/python/existing_rtl/verify_repair.pyscript4.6 KB
scripts/python/existing_rtl/verify_repair_core.pyscript45.7 KB
scripts/python/existing_rtl/verify_repair_patch_apply.pyscript23.5 KB
scripts/python/existing_rtl/verify_repair_patch_categories.pyscript35.5 KB
scripts/python/existing_rtl/verify_repair_patch_plan.pyscript25.1 KB
scripts/python/existing_rtl/verify_repair_patching.pyscript2.4 KB
scripts/python/existing_rtl/verify_repair_support.pyscript25.6 KB
scripts/python/existing_rtl/verify_repair_testbench.pyscript45.9 KB
scripts/python/existing_rtl/verify_reporting.pyscript16.1 KB
scripts/python/facade/__init__.pyscript45 B
scripts/python/facade/existing_rtl_api.pyscript14.0 KB
scripts/python/facade/quality_api.pyscript19.9 KB
scripts/python/facade/representative_cases.pyscript38.3 KB
scripts/python/facade/verilog_api.pyscript6.5 KB
scripts/python/facade/workflow_api.pyscript63.2 KB
scripts/python/generation/tb_generator.pyscript54.9 KB
scripts/python/header_contract.pyscript21.1 KB
scripts/python/installation/__init__.pyscript52 B
scripts/python/installation/bundle.pyscript16.3 KB
scripts/python/installation/catalog.pyscript16.6 KB
scripts/python/installation/cli.pyscript26.4 KB
scripts/python/installation/projection.pyscript14.2 KB
scripts/python/installation/receipt.pyscript13.4 KB
scripts/python/installation/transaction.pyscript29.0 KB
scripts/python/quality/clock_name_roles.pyscript1.0 KB
scripts/python/quality/comment_placement.pyscript49.5 KB
scripts/python/quality/declaration_region_policy.pyscript8.0 KB
scripts/python/quality/deliverable_gate.pyscript51.9 KB
scripts/python/quality/external_interface_stubs.pyscript41.5 KB
scripts/python/quality/formatter_ast.pyscript85.0 KB
scripts/python/quality/formatter_ast_instances.pyscript5.4 KB

scripts/python/existing_rtl/verify_reporting.py

View on GitHub
"""组装 existing RTL verify-repair 流程的结构化报告。"""

# 延迟类型注解求值,保持运行时导入成本稳定
from __future__ import annotations

# 标准类型依赖用于表达 JSON payload 的宽松结构
from typing import Any

# workflow router 提供诊断分流标签,报告层只消费其结果
from scripts.python.workflow.workflow_router import classify_diagnosis_route

# 诊断 outcome 到人工可读 bug class 的映射保持独立,避免报告函数堆叠分支
def _bug_class_for_outcome(diagnosis: dict[str, Any]) -> str:
    """把验证诊断 outcome 映射为报告层 bug class。

    参数:
        diagnosis: 验证诊断结果,通常包含 outcome 字段。
    返回:
        兼容既有报告 wire shape 的 bug class 字符串。
    """

    # outcome 先转成字符串,兼容诊断 payload 中的 None 或枚举式对象
    str_outcome = str(diagnosis.get("outcome"))  # 诊断结果标签

    # compile 错误优先归入编译类,便于上层提示先看工具日志
    if str_outcome == "compile_error":

        # 返回 wire shape 既有的 bug class 字符串
        return "compile"

    # assertion 失败通常说明协议或 RTL 逻辑不满足测试约束
    if str_outcome == "assertion_fail":

        # 保持既有 payload 中的分类文本
        return "protocol_or_logic"

    # protocol violation 需要保留 timing 可能性,供修复计划选择检查路径
    if str_outcome == "protocol_violation":

        # 返回兼容原 JSON 的协议/时序分类
        return "protocol_or_timing"

    # timeout 更接近活性问题,避免误导为单点组合逻辑错误
    if str_outcome == "timeout":

        # 返回既有 liveness 分类
        return "liveness"

    # pass 表示没有待归因缺陷
    if str_outcome == "pass":

        # 返回 none 保持 downstream 字段值兼容
        return "none"

    # not_run 表示验证没有执行,不能推断具体 bug class
    if str_outcome == "not_run":

        # 返回 not_run 保留未执行状态
        return "not_run"

    # 未知 outcome 交给调用方以保守方式展示
    return "unknown"

# 仿真片段报告保留 compile/simulation 摘要与 testbench 标签观测
def simulation_slice_payload(
    *,
    compile_log: str,
    simulation_log: str,
    executed: bool,
    tb_contract: dict[str, Any],
    excerpt_fn: Any,
) -> dict[str, Any]:
    """
    生成仿真日志切片报告。

    :param compile_log: 编译阶段完整日志文本。
    :param simulation_log: 仿真阶段完整日志文本。
    :param executed: 仿真命令是否实际执行。
    :param tb_contract: testbench 契约,包含日志标签和 transcript 前缀。
    :param excerpt_fn: 日志截断函数,用于生成可读摘要。
    :return: 保持 wire shape 兼容的仿真日志切片 payload。
    """

    # 只记录真实出现在仿真日志中的 testbench 标签
    list_tb_tags = [tag for tag in tb_contract.get("log_tags", []) if tag in simulation_log]  # 日志中命中的 TB 标签

    # 返回给上层报告写入器的稳定 JSON payload
    return {
        "version": 1,
        "executed": executed,
        "compile_excerpt": excerpt_fn(compile_log),
        "simulation_excerpt": excerpt_fn(simulation_log),
        "observed_tags": list_tb_tags,
        "transcript_prefix": tb_contract.get("transcript_prefix"),
    }

# timing diagnostic 报告提取诊断归因和验证计划焦点
def timing_diagnostic_payload(
    diagnosis: dict[str, Any],
    *,
    validation_report: Any,
    verification_plan: dict[str, Any],
) -> dict[str, Any]:
    """
    生成时序/协议诊断 payload。

    :param diagnosis: 验证诊断结果,至少包含 outcome 与 findings。
    :param validation_report: 验证报告对象,需提供 ok() 方法。
    :param verification_plan: 验证计划,包含 focus_signals 等定位信息。
    :return: 面向修复报告的诊断摘要 payload。
    """

    # 将 outcome 归一到报告层展示的 bug class
    str_bug_class = _bug_class_for_outcome(diagnosis)  # 报告层缺陷分类

    # 返回诊断摘要,字段名保持既有 wire shape 不变
    return {
        "version": 1,
        "outcome": diagnosis.get("outcome"),
        "bug_class": str_bug_class,
        "validation_ok": bool(validation_report.ok()),
        "focus_signals": verification_plan.get("focus_signals", []),
        "findings": diagnosis.get("findings", []),
    }

# expected trace markdown 是分析结果和验证 checkpoint 的人读摘要
def expected_trace_markdown(analysis: dict[str, Any], verification_plan: dict[str, Any]) -> str:
    """
    生成 expected trace Markdown 摘要。

    :param analysis: RTL 分析结构,包含 module_info.name。
    :param verification_plan: 验证计划,包含 verification_targets 列表。
    :return: 描述 checkpoint、signals 与 expectation 的 Markdown 文本。
    """

    # 模块名用于报告标题,与生成工件的 RTL 模块保持一致
    str_module_name = str(analysis["module_info"]["name"])  # Expected Trace 标题模块名

    # checkpoint 列表来自 verification plan,缺失时生成兜底行
    list_checkpoints = verification_plan.get("verification_targets", [])  # 待展示的验证 checkpoint

    # 表格头保留英文文本,保证已有快照和文档比较稳定
    list_lines = [
        f"# Expected Trace: {str_module_name}",  # 报告标题中的 RTL 模块名
        "",  # 标题与来源说明之间的 Markdown 间隔
        "This trace is analysis-derived and used as a stable semantic checkpoint summary.",  # trace 来源说明
        "",  # 来源说明与 checkpoint 表格之间的 Markdown 间隔
        "| Step | Checkpoint | Signals | Expectation |",  # checkpoint 表格列名
        "| --- | --- | --- | --- |",  # Markdown 表格列对齐标记
    ]  # checkpoint 明细追加前必须先输出的标题、来源说明和表头

    # 逐个 checkpoint 生成表格行,按 1 起始序号匹配人读报告习惯
    for int_index, dict_checkpoint in enumerate(list_checkpoints, start=1):

        # signals 字段为空时写成 n/a,避免报告单元格留空
        str_signals = ", ".join(dict_checkpoint.get("signals", [])) or "n/a"  # checkpoint 关注信号文本

        # description 是最适合作为 expectation 的人读说明
        str_description = dict_checkpoint.get("description")  # checkpoint 描述文本

        # name 作为 description 缺失时的次级兜底
        str_checkpoint_name = dict_checkpoint.get("name")  # checkpoint 名称文本

        # expectation 优先使用描述,其次回退到 checkpoint 名称
        str_expectation = str(str_description or str_checkpoint_name or "analysis-derived behavior")  # checkpoint 期望行为文本

        # 追加当前 checkpoint 的 Markdown 表格行
        list_lines.append(
            f"| {int_index} | {dict_checkpoint.get('check_id', f'checkpoint_{int_index}')} | "
            f"{str_signals} | {str_expectation} |"
        )

    # 只有表头时写入兜底 checkpoint,明确说明分析未推断出检查点
    if len(list_lines) == 6:

        # 追加无 checkpoint 的显式占位行,保持表格结构完整
        list_lines.append("| 1 | no_checkpoints | n/a | No verification checkpoints were inferred. |")

    # Markdown 末尾保留一个空行,匹配原报告格式
    list_lines.append("")

    # 返回完整 Markdown 文本供文件写入器保存
    return "\n".join(list_lines)

# waveform diff payload 记录波形检查状态和人工复核摘要
def waveform_diff_payload(
    diagnosis: dict[str, Any],
    *,
    verification_plan: dict[str, Any],
    executed: bool,
) -> dict[str, Any]:
    """
    生成波形差异检查 payload。

    :param diagnosis: 验证诊断结果,包含 outcome 与 findings。
    :param verification_plan: 验证计划,包含 focus_signals。
    :param executed: 波形检查是否实际执行。
    :return: 波形差异状态 payload。
    """

    # 返回波形检查摘要,保持 pass/pending_review 状态文本不变
    return {
        "version": 1,
        "executed": executed,
        "status": "pass" if diagnosis.get("outcome") == "pass" else "pending_review",
        "focus_signals": verification_plan.get("focus_signals", []),
        "summary": diagnosis.get("findings", []),
    }

# testcase matrix payload 将验证计划转换为 TB 覆盖矩阵
def testcase_matrix_payload(
    verification_plan: dict[str, Any],
    *,
    tb_contract: dict[str, Any],
    diagnosis: dict[str, Any],
) -> dict[str, Any]:
    """
    生成 testcase 覆盖矩阵 payload。

    :param verification_plan: 验证计划,包含 verification_targets。
    :param tb_contract: testbench 契约,包含 tb_mode 与 log_tags。
    :param diagnosis: 验证诊断结果,用于判断 case 是否被编译错误阻断。
    :return: 描述 TB mode 与 case 覆盖状态的 payload。
    """

    # 收集每个 verification target 对应的 testcase 行
    list_cases = []  # 验证计划转换后的 testcase payload 行

    # 按验证计划顺序生成 case,保证报告稳定可比较
    for int_index, dict_target in enumerate(verification_plan.get("verification_targets", []), start=1):

        # 追加单个 testcase 行,字段名保持既有 JSON 契约
        list_cases.append(
            {
                "case_id": dict_target.get("check_id", f"checkpoint_{int_index}"),
                "category": dict_target.get("category", "behavior"),
                "signals": dict_target.get("signals", []),
                "expectation": dict_target.get("description")
                or dict_target.get("name")
                or "analysis-derived verification target",
                "log_tags": tb_contract.get("log_tags", []),
                "status": "covered" if diagnosis.get("outcome") != "compile_error" else "blocked_by_compile",
            }
        )

    # 返回 testbench 模式和 case 矩阵
    return {"version": 1, "tb_mode": tb_contract.get("tb_mode"), "cases": list_cases}

# run summary payload 汇总验证循环终态和 RTL/TB 变更状态
def run_summary_payload(
    *,
    diagnosis: dict[str, Any],
    validation_report: Any,
    tb_contract: dict[str, Any],
    rtl_mutation: dict[str, Any],
) -> dict[str, Any]:
    """
    生成 verify-repair 单轮运行摘要。

    :param diagnosis: 验证诊断结果,包含 outcome。
    :param validation_report: 验证报告对象,需提供 ok() 方法。
    :param tb_contract: testbench 契约,包含模式与语言。
    :param rtl_mutation: RTL 修复记录,包含 applied 与 confirmation_required。
    :return: 面向上层 workflow 的运行摘要 payload。
    """

    # diagnosis route 由 workflow router 统一分类,报告层不复制分流规则
    str_diagnosis_route = classify_diagnosis_route(  # 运行摘要使用的诊断分流标签
        diagnosis=diagnosis,  # 诊断分流依据的 outcome/findings payload
        validation_report=validation_report,  # 诊断分流依据的验证报告对象
        tb_contract=tb_contract,  # 诊断分流依据的 testbench 契约
    )

    # 先创建摘要字典,再逐项填充以避免大字面量遮住字段来源
    dict_summary = {"version": 1}  # run summary payload 基础结构

    # status 固定表示本轮 verify-repair 已走到摘要阶段
    dict_summary["status"] = "completed"  # 运行摘要状态

    # outcome 透传诊断阶段产出的终态标签
    dict_summary["outcome"] = diagnosis.get("outcome")  # 验证诊断 outcome

    # diagnosis route 标明后续报告应优先查看的诊断方向
    dict_summary["diagnosis_route"] = str_diagnosis_route  # 诊断分流标签

    # validation_ok 统一转成 bool,屏蔽报告对象实现细节
    dict_summary["validation_ok"] = bool(validation_report.ok())  # 验证报告通过标志

    # testbench 模式保留给上层报告展示 TB 生成策略
    dict_summary["tb_mode"] = tb_contract.get("tb_mode")  # 报告展示用 testbench 模式

    # testbench 语言字段保留给报告兼容层
    dict_summary["tb_language"] = tb_contract.get("tb_language")  # 报告展示用 testbench 语言

    # RTL patch 状态说明本轮是否修改过设计文件
    dict_summary["rtl_patch_applied"] = bool(rtl_mutation.get("applied"))  # RTL 修改应用状态

    # confirmation_required 保留人工确认边界,避免自动修复越权
    dict_summary["confirmation_required"] = bool(rtl_mutation.get("confirmation_required"))  # 人工确认需求

    # 返回运行摘要,字段名保持下游消费兼容
    return dict_summary

# synth readiness payload 暴露仿真后端选择和综合准备状态
def synth_readiness_payload(validation_report: Any, *, readiness: str) -> dict[str, Any]:
    """
    生成 synthesis readiness payload。

    :param validation_report: 验证报告对象,需提供 to_dict() 与 ok() 方法。
    :param readiness: 调用方请求的 readiness 模式,例如 implement。
    :return: 描述工具执行、后端选择和 readiness 请求的 payload。
    """

    # metrics 承载验证阶段记录的工具链选择和缺失后端信息
    dict_metrics = validation_report.to_dict().get("metrics", {})  # 验证报告指标字段

    # 返回综合准备状态,保留既有字段名供报告和测试消费
    return {
        "version": 1,
        "requested_readiness": readiness,
        "selected_simulator_backend": dict_metrics.get("selected_simulator_backend"),
        "executed_tools": dict_metrics.get("executed_tools", []),
        "missing_preferred_backends": dict_metrics.get("missing_preferred_backends", []),
        "selection_policy": dict_metrics.get("selection_policy"),
        "implement_requested": readiness == "implement",
        "validation_ok": bool(validation_report.ok()),
    }

# terminal status payload 是 verify-repair 对外暴露的最终状态摘要
def terminal_status_payload(
    *,
    diagnosis: dict[str, Any],
    validation_report: Any,
    tb_contract: dict[str, Any] | None = None,
    tb_mutation: dict[str, Any],
    rtl_mutation: dict[str, Any],
) -> dict[str, Any]:
    """
    生成 verify-repair 终态 payload。

    :param diagnosis: 验证诊断结果,包含 outcome。
    :param validation_report: 验证报告对象,需提供 ok() 方法。
    :param tb_contract: 可选 testbench 契约,缺失时按空契约分类。
    :param tb_mutation: testbench 变更记录,包含 applied。
    :param rtl_mutation: RTL 变更记录,包含 applied。
    :return: 描述验证终态、变更状态和用户可读消息的 payload。
    """

    # 只有诊断 pass 且验证报告 ok 时,才认为 verify-repair 达到成功终态
    bool_success = diagnosis.get("outcome") == "pass" and validation_report.ok()  # 终态成功标志

    # 空 TB 契约按空字典处理,避免分类器收到 None
    dict_tb_contract = tb_contract or {}  # 诊断分类使用的 TB 契约

    # diagnosis route 复用 workflow router 的统一分类规则
    str_diagnosis_route = classify_diagnosis_route(  # 终态 payload 使用的诊断分流标签
        diagnosis=diagnosis,  # 终态分流依据的 outcome/findings payload
        validation_report=validation_report,  # 终态分流依据的验证报告对象
        tb_contract=dict_tb_contract,  # 终态分流依据的 testbench 契约
    )

    # 返回 verify-repair 最终状态,message 文本保持原有英文契约
    return {
        "version": 1,
        "success": bool_success,
        "outcome": diagnosis.get("outcome"),
        "diagnosis_route": str_diagnosis_route,
        "validation_ok": bool(validation_report.ok()),
        "tb_mutation_applied": bool(tb_mutation.get("applied")),
        "rtl_mutation_applied": bool(rtl_mutation.get("applied")),
        "message": "Verification loop reached a clean PASS state."
        if bool_success
        else "Verification loop did not reach a terminal PASS state.",
    }
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall