opencode-qa

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 68k 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.

Installation

Add opencode-qa to your agent with:

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

Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.

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

When to use it

Reach for opencode-qa when you want testing help from opencode without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.

Strengths

• Ships in code-yeongyu/oh-my-openagent, an established project with 68,032 GitHub stars
• Declares compatibility with opencode
• Actively maintained (recent commits)

Things to check

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

Topics

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 declares compatibility with opencode. Agent Skills use a portable SKILL.md format, so other compatible clients can usually load it too.

Where does opencode-qa come from?

opencode-qa ships inside code-yeongyu/oh-my-openagent, a repository that contains 46 catalogued skills in total. The repository's 68,032 GitHub stars apply to that whole collection, not to this skill on its own.