Comma

Report types

Anything that writes HTML.

Comma renders the HTML you give it rather than parsing a format, so the list below is not a list of integrations — it is 324 guides to the specific quirks of 324 tools. Where each one writes its output, which references break when you open it from disk, and what to upload alongside the entry file.

Test results

Unit, integration and end-to-end runs. Publish red builds too — those are the ones with a reader.

Visual regression & device labs

Pixel diffs and cross-device runs, where the person who can approve the change is usually the one without a seat.

Coverage

Line and branch coverage trees, where the drill-down is the whole point.

Security scans

Dependency advisories, SAST findings and infrastructure scans. Keep these on a restricted access setting.

Code quality

Linters and static analysis, where a backlog only gets cleared if people can claim it.

LLM & model evals

Scores that are proxies for a judgment call — which means the person who can settle them is rarely the person who ran the eval.

Notebooks & data

Analysis that has to stay interactive to be worth reading.

Diagrams & architecture

Diagrams-as-code and whiteboard exports, which render in your editor and as raw text everywhere a decision gets signed off.

Charts & maps

Single-file visualizations, and how to keep them from going blank in transit.

BI & observability dashboards

Live dashboards behind a login. Getting the numbers to the people who decide on them, without buying them a seat.

Data apps

Python and R apps that need a running process — and what to publish when the reader only wants the findings.

Profiles & flame graphs

CPU, memory and allocation profiles. The interaction is the finding, which is exactly what a screenshot removes.

Performance & bundles

Load tests, profiles and bundle treemaps — regressions are visible as revisions.

Accessibility

The findings split across design and engineering, so the report has to reach both.

Infrastructure plans & runs

The diff between what exists and what is about to. Read once, by someone who has to approve it.

Static sites & framework builds

A folder of HTML that needs somewhere to live before it is a site, and dies the moment it is opened from the filesystem.

Docs & API references

Generated documentation — most of which loses its search box when opened from the filesystem.

Slides

Decks that lose their point the moment they are flattened to PDF.

Sharing & hosting

The general problem: getting an HTML file to somebody without a server.

Your tool isn’t listed

It still works. The guides differ because each tool writes its output somewhere different and breaks in its own way; the publishing step is the same one every time — upload the entry HTML, upload the folder alongside it, get a URL. Start with sharing an HTML report or publishing from CI.