How do I generate a shareable RuboCop report?

Run `rubocop --format html --out rubocop.html` (add `--format progress` first if you still want terminal output). Then drag the file into Comma or PATCH it to the API — you get a URL instead of a scrollback buffer.

Can I get both terminal output and an HTML file?

Yes. RuboCop accepts multiple formatters: `rubocop --format progress --format html --out rubocop.html` prints the usual progress dots and writes the HTML file at the same time.

Why publish a lint report at all?

Because the useful conversation about lint is not 'there are 812 offenses', it is 'should this cop be enabled for this directory'. That conversation needs the offense list in front of everyone, and a place to write the answer down.

How do I publish from CI?

PATCH the same report id from the job. RuboCop exits non-zero on offenses, so run the publish step with `if: always()` or the only runs that publish are the clean ones.

Does the report stay interactive at the URL?

Yes. Report HTML renders with scripts enabled inside a sandboxed iframe, so the per-file expanders and the offense summary behave as they do locally.

Share a RuboCop report

A big Ruby codebase adopting RuboCop produces a number nobody can act on: 812 offenses detected. The terminal output that explains it is four thousand lines long and lives in a CI log that expires.

RuboCop ships an HTML formatter for exactly this:

rubocop --format progress --format html --out rubocop.html

Two formatters, one command: dots in the terminal, a browsable report on disk. It groups by file, expands to the offending source line, and links each offense to the cop that raised it.

Publish it

Drag rubocop.html into the app, or from CI:

bundle exec rubocop --format html --out rubocop.html || true

curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html rubocop.html \
        --arg title "RuboCop — $GITHUB_SHA" '{title: $title, html: $html}')"

Run the publish step with if: always() (GitHub Actions), when: always (GitLab, CircleCI) or post { always { … } } (Jenkins). A clean lint report is not the one anyone needs.

The conversation lint actually needs

Style enforcement is a social negotiation with a config file attached. The decisions are worth keeping:

Anchored threads on the cop or the file — "we're disabling Metrics/ClassLength for app/services, here's why". See commenting on HTML.
Revisions — one report id per repo, one revision per run, so a .rubocop_todo.yml regeneration shows up as movement instead of a vibe.
Access per report — private, team, domain-gated, or named reviewers. See the sharing model.

Let the agent read the offenses

If a coding agent is doing the cleanup, point it at the report through MCP: it can read the published offenses and the human comments on them in the same call, which is a cheaper context than re-running the linter and re-deriving what the team already decided. See give an agent feedback.

Limits

Entry HTML: 5 MB. An 800-offense report is comfortably under; a 50,000-offense first run may not be — scope with --only or by directory.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a lint report →