Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

Codex QA (omo plugin verification)

An isolated-environment QA skill that proves omo Codex plugin hooks, installer, and TUI work without ever touching your real ~/.codex.

Dev & CodingAdvanced★ 67,531⑂ 5,507AI score 6/10Last updated: Aug 9, 2026

What it does

QAs the omo Codex Light plugin (packages/omo-codex, shipped as lazycodex) in strict isolation.

  • Spins up a throwaway CODEX_HOME plus a LOCAL mock model provider so a real codex app-server runs with zero real API calls.
  • Proves a hook actually fired via the first-party hook/started / hook/completed notification stream instead of scraping logs.
  • Covers isolated install verification (install-verify.sh), deterministic per-component hook probes (hook-unit-probe.sh), a tmux TUI smoke test (tui-smoke.sh), and runtime log observation (RUST_LOG / logs SQLite / /debug-config).
  • Every helper script ships a --self-test, so the QA tooling doubles as its own regression suite.
  • Shasums ~/.codex/config.toml before and after to prove your real setup stayed clean, and writes artifacts to .omo/evidence/<date>-<slug>/.

Who it's for

  • Contributors to oh-my-openagent / lazycodex who touch packages/omo-codex.
  • Developers who need safe regression checks on Codex plugin hooks, components, and installers.
  • Anyone studying an isolated-QA pattern that never pollutes the real dev environment.

Examples

  1. Prove a hook fires: ask "verify the userPromptSubmit hook fires in a live turn" → run scripts/app-server-drive.sh --plugin and save the hook/completed notification as JSON evidence.
  2. Validate installer changes: after editing src/install/*, run scripts/install-verify.sh --self-test to confirm omo@sisyphuslabs is enabled and component binaries / agent TOMLs are linked inside the sandbox home.
  3. TUI smoke + visual evidence: use scripts/tui-smoke.sh to confirm the real TUI boots and survives, then render through the xterm.js web terminal helper when true-color / CJK-width PNG evidence is required.

· · · Install guide · · ·

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 /tmp/oh-my-openagent && mkdir -p ~/.claude/skills && cp -r /tmp/oh-my-openagent/.agents/skills/codex-qa ~/.claude/skills/

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

  1. Open a terminal and clone the repo: git clone https://github.com/code-yeongyu/oh-my-openagent.git /tmp/oh-my-openagent
  2. Create the skills folder: mkdir -p ~/.claude/skills
  3. Copy the skill in: cp -r /tmp/oh-my-openagent/.agents/skills/codex-qa ~/.claude/skills/
  4. Install prerequisites: codex (codex-cli 0.140.0 or newer recommended), node, jq, tmux, and bun.
  5. Restart Claude Code, then ask for "codex qa" or "verify codex hook" to trigger the skill.
  6. Run the one-time check: bash ~/.claude/skills/codex-qa/scripts/lib/common.sh --self-check to validate deps and the isolation harness.
  7. Run actual QA from the root of a repo that contains packages/omo-codex so the script paths resolve.
View source on GitHub ↗License: NOASSERTION