opencode-qa

QA opencode itself, per case: verify the CLI/terminal (opencode run, db, serve, export), prove a specific plugin hook/action/event fired via the SSE event stream, smoke-test the TUI under tmux, and investigate sessions in opencode's SQLite DB by id, title/name, or message text. Ships tested helper scripts (each with a --self-test) plus per-domain references. Use whenever someone wants to QA, smoke-test, verify, or debug opencode's CLI, HTTP server, plugin hooks/events, or TUI, or to find/inspect opencode sessions in the database. Triggers: opencode qa, qa opencode, test opencode, verify opencode hook, opencode session db, find opencode session by id/name/text, opencode tui test, opencode server health, opencode event stream.

by code-yeongyu 69k GitHub stars Other Updated Sep 21, 2026
↑ GrowingActive Testing CodexCursorOpenCode ⚠ No license
opencode-qa skill by code-yeongyu
opencode-qa — Testing skill by code-yeongyu

Overview

opencode-qa is an open-source testing skill for OpenCode, published by code-yeongyu. Its author describes it as: “QA opencode itself, per case: verify the CLI/terminal (opencode run, db, serve, export), prove a specific plugin hook/action/event fired via the SSE event stream, smoke-test the TUI under tmux, and investigate session…”. The project has 69k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/opencode-qa`.

What opencode-qa does

QA the opencode coding agent itself. This skill maps each QA need to a tested helper script and a deep reference. Every script ships a `--self-test` that asserts its scenario against the live machine, so the scripts are both the QA tools and their own regression checks.

Best for

What’s inside

The SKILL.md for opencode-qa is organised into these sections:

  • Golden rules (read before running anything)
  • Setup
  • Router: pick your case
  • Case A: CLI / terminal works
  • Case B: a specific hook, action, or event
  • Case C: the TUI
  • Case D: investigate sessions in the DB
  • Scripts index
  • Risks and caveats
  • References

Installation

Add opencode-qa to your agent with:

git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/opencode-qa

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Codex — declared in the repository topics
  • Cursor — declared in the repository topics
  • OpenCode — named in the skill.md

License

code-yeongyu has not declared a standard open-source license for this repository (Other). Confirm the terms with the author before reusing it.

Strengths

  • Ships in code-yeongyu/oh-my-openagent, an established project with 69,248 GitHub stars
  • Works with Codex, Cursor, OpenCode
  • Actively maintained — repository updated in the last 30 days
  • Its repository gained 2,357 GitHub stars over the last 52 days

Things to check

  • No license declared — confirm terms with the author before reuse

Author

code-yeongyu 49 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does opencode-qa do?
QA opencode itself, per case: verify the CLI/terminal (opencode run, db, serve, export), prove a specific plugin hook/action/event fired via the SSE event stream, smoke-test the TUI under tmux, and investigate sessions in opencode's SQLite DB by id, title/name, or message text. Ships tested helper scripts (each with a --self-test) plus per-domain references. Use whenever someone wants to QA, smoke-test, verify, or debug opencode's CLI, HTTP server, plugin hooks/events, or TUI, or to find/inspect opencode sessions in the database. Triggers: opencode qa, qa opencode, test opencode, verify opencode hook, opencode session db, find opencode session by id/name/text, opencode tui test, opencode server health, opencode event stream.
How do I install opencode-qa?
Run git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/opencode-qa in your agent, then reload your skills. Review the source at https://github.com/code-yeongyu/oh-my-openagent before installing.
Is opencode-qa free to use?
opencode-qa is publicly available on GitHub, but code-yeongyu has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
Which agents does opencode-qa work with?
opencode-qa lists Codex, Cursor, and OpenCode — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does opencode-qa come from?
opencode-qa ships inside code-yeongyu/oh-my-openagent, a repository that contains 49 catalogued skills in total. The repository's 69,248 GitHub stars apply to that whole collection, not to this skill on its own.

QA the omo Senpi adapter (packages/omo-senpi, packages/senpi-task) against the REAL senpi binary in strict isolation, and write every artifact to the one canonical evidence path .omo/evidence/omo-senpi-adapter/<slug>/. The live drivers under packages/omo-senpi/scripts/qa/ create their own isolated SENPI_CODING_AGENT_DIR and ignore the caller's, so the real ~/.senpi/agent is never written. Ships scripts/resolve-evidence-dir.mjs, which is the ONLY sanctioned way to pick an evidence directory: it rejects traversal, separators, absolute paths, and stray roots such as local-ignore/qa-evidence. Use whenever someone changes anything under packages/omo-senpi or packages/senpi-task, or wants to QA, smoke-test, verify, or debug the Senpi adapter, the task/team engine, the DAG, task RPC, or skill delivery. Triggers: senpi qa, qa senpi, senpi-qa, test senpi adapter, verify senpi task, senpi task e2e, senpi team e2e, task dag qa, live senpi driver, senpi evidence path.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Claude CodeCodexCursor+3
38k GitHub stars MIT Updated Jul 22, 2026 Free