# Preview My Work

Boot, reopen, update, or reset an isolated OmniRush.ai PR preview inside Codex.

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

## Install

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

## Description

Boot, reopen, update, or reset an isolated OmniRush.ai PR preview inside Codex. Use Den in the in-app browser or the real Linux Electron app streamed through Daytona noVNC for hands-on testing.

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

# Preview my work

Use the repository's world lifecycle. These are disposable test environments,
not production or a user's installed desktop profile. Do not touch another
world or an existing test sandbox. Run from the requested worktree.

## Choose a preview

- `preview-den`: signup, team administration, onboarding, connectors, policies.
- `preview-desktop`: real Electron plus its own Den; workspaces, chat and native
  app interactions. This is Linux Electron, not a macOS/Windows parity check.

Choose `--scenario fresh` for signup/first use, `team` for an owner with Notion
and Linear available (individual accounts remain unconnected), `restricted`
for that team with the API's canonical restricted policy values, or `workspace`
for a signed-in desktop workspace without pre-added tools. Fresh desktop creates
its local workspace but does not sign into Den. No model credentials are seeded.
Do not describe these fixtures as capable of live model/provider requests.

## Start and open

Use a unique stage such as `pr-1234` to keep previews separate. First inspect
`pnpm world list` and `pnpm world outputs <world> --stage <stage> --json`.
An existing matching world should be reopened, not recreated. Compare its
recorded scenario and ref before adopting it. A stage is not a git ref.

Use reviewed repository code: previews execute that ref’s build scripts. Do not
load production credentials or attach shared secrets volumes. Push the intended
commit and use its full 40-character SHA so Daytona can fetch it. Both launch
and update reject mutable branch names. Then:

```sh
OMNIRUSH_EVAL_REF=<pushed-sha> infisical run --silent --env dev -- pnpm world up preview-den --stage pr-1234 --place daytona --detach --timeout 600000 -- --scenario fresh --lifetime 120
```

The rest: https://github.com/omnirush-ai/omnirush-gui/blob/HEAD/.opencode/skills/preview-my-work/SKILL.md