Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Codex QA (omo Codex Light verification)

QA the omo Codex plugin in a fully isolated CODEX_HOME with a mock model, proving hooks actually fire without ever touching the user's real ~/.codex.

Dev & CodingAdvanced★ 69,295⑂ 5,711AI score 8/10Last updated: Sep 22, 2026

What it does

  • Exercises the packages/omo-codex (lazycodex) plugin against a real codex binary but inside an isolated CODEX_HOME with a local mock model provider — no real API calls, and the user's ~/.codex is never read or written.
  • Proves a hook fired the first-party way: via codex app-server hook/started / hook/completed notifications instead of scraping logs.
  • Provides a router table matching QA path to change scope: component hook probes (hook-unit-probe.sh), installer/config.toml checks (install-verify.sh), live session drive (app-server-drive.sh --plugin), and a tmux TUI smoke test (tui-smoke.sh).
  • Every helper script ships a --self-test, doubling as its own regression check, and shasums ~/.codex/config.toml before/after to prove the real home stayed clean.
  • Forces evidence capture into .omo/evidence/<date>-<slug>/ — no artifact means the QA did not happen.

Who it's for

  • Contributors and maintainers of the oh-my-openagent repo working on packages/omo-codex.
  • Developers who changed Codex plugin hooks, components, or the installer and need regression proof.
  • Anyone looking for a solid pattern for safely QA-ing a CLI plugin without polluting personal config.

Examples

  1. After editing hook logic: run scripts/hook-unit-probe.sh --self-test to pin the ultrawork component's exact stdout, then scripts/app-server-drive.sh --plugin to prove the live wiring emits hook/completed.
  2. After touching the installer: scripts/install-verify.sh --self-test confirms omo@sisyphuslabs is enabled in the isolated config.toml and component binaries/agent TOMLs are linked.
  3. When TUI visual evidence is needed: tui-smoke.sh verifies the TUI boots and survives, then web-terminal-visual-qa.mjs renders it through xterm.js for true-color screenshots without tmux's color/CJK degradation.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/HEAD/.agents/skills/codex-qa/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .agents/skills/codex-qa folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/codex-qa/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/code-yeongyu/oh-my-openagent.git && mkdir -p ~/.claude/skills && cp -r oh-my-openagent/.agents/skills/codex-qa ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Install prerequisites: node, jq, tmux, bun, and the codex CLI (verified against 0.140.0). Check with codex --version.
  2. Clone the repo: git clone https://github.com/code-yeongyu/oh-my-openagent.git
  3. Copy the skill: mkdir -p ~/.claude/skills && cp -r oh-my-openagent/.agents/skills/codex-qa ~/.claude/skills/
  4. Restart Claude Code and confirm the skill is picked up (try a prompt like "codex qa").
  5. Before the first run, from the skill directory execute bash scripts/lib/common.sh --self-check to validate dependencies and the isolation harness.
  6. Run the actual QA from inside the oh-my-openagent working tree; prefer the Docker surface via script/agent/qa-docker.sh when available.
  7. Store outputs under .omo/evidence/<date>-<slug>/ and verify the script output asserting your real ~/.codex is unchanged.
View source on GitHub ↗License: NOASSERTION