Commands  ›  Clash Manager / Reporting  ›  Clash Manager Export Results To Excel

Clash Manager Export Results To Excel

Clash Manager / Reporting writes to model Public API · not yet exposed

Coming soon

Before you run this

Active doc; ClosedXML available; staging DB has ≥ 1 row.

After it runs

Single .xlsx on disk.

When to use this

Don't use this when

PDF / Word / HTML — dedicated commands.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Resolve output path (default .mepbridge/qa/reports/clashes_{ts}.xlsx).
2) Resolve image root (default .mepbridge/qa/images).
3) Delegate to SaveClashResultsToExcelFile.WriteReport.
4) Open on Human path.
5) Emit ok + output_path + rows.

What you'll see in the chat

on start
Exporting clashes to Excel…
thinking
Resolving default paths…
Delegating to SaveClashResultsToExcelFile…
on success
Excel written at {output_path}.
on failure
Excel export failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_manager_export_results_to_excel
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashmanagerexportresultstoexcel · export clash excel · qa xlsx report

PillarClash Manager / Reporting