# Publish Evidence

Publish test evidence, publish all test runs, update PR verification, audit red...

- Repository: https://github.com/omnirush-ai/omnirush-gui (4595 stars)
- Category: Testing
- License: see repository
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add omnirush-ai/omnirush-gui --skill publish-evidence -g -a claude-code -y`
Codex: `npx skills add omnirush-ai/omnirush-gui --skill publish-evidence -g -a codex -y`
Cursor: `npx skills add omnirush-ai/omnirush-gui --skill publish-evidence -g -a cursor -y`
Gemini CLI: `npx skills add omnirush-ai/omnirush-gui --skill publish-evidence -g -a gemini-cli -y`

## Description

Publish test evidence, publish all test runs, update PR verification, audit red evidence, prove a PR, or declare a PR verdict. Use after @omnirush/testkit runs.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill: Publish Evidence

The orchestrator owns this verdict and human-verification step. It derives the
verdict from completed evidence; publishing makes that verdict inspectable and
never reruns a test.

## Declare the verdict

- `Passed`: every claim has an observable assertion in the completed test run.
- `Failed`: an assertion disproves at least one expected outcome.
- `Incomplete`: requirements, tooling, or evidence are missing. A skip is always
  `Incomplete`, never `Passed`.
- Prose, screenshots, and recordings do not decide the verdict.

## Make every claim auditable

- Show the test name and verdict, each claim's assertion evidence, the relevant
  test artifacts, the source test run, and the reproduction command.
- Publish one compact sticky comment linking to a report with a section for every
  claimed test. The report must show assertion evidence and original records.
  When the review app is not configured, keep those sections in the comment.
  If a claim has no inspectable evidence, report the PR `Incomplete`.
- Write the `<!-- test-evidence -->` marker. The publisher recognizes old sticky
  markers only to update comments created before the migration.

## Publish the PR head

Run checks on the final PR head after any rebase or cherry-pick. Test runs are
bound to a commit SHA, so history rewrites require rerunning and republishing.
After a multi-test run, publish the complete selection together:

```bash
pnpm evals:e2e --publish --pr <n> --all
# Or select runs explicitly; repeat --test-run for each claimed run.
pnpm evals:e2e --publish --pr <n> --test-run <dir|name> --test-run <dir|name>
```

`--all` selects stored runs matching the current PR head. Include a DocShot
receipt with `--docshot <image.png.review.json>`. It must match that commit too.
Names and captions provide the default report; `--title` and repeatable `--gap`
are optional context. No separate report-writing step is required.

The rest: https://github.com/omnirush-ai/omnirush-gui/blob/HEAD/.opencode/skills/publish-evidence/SKILL.md