opencode-qa

Validate OpenCode agent integrity via CLI, HTTP, and TUI smoke tests.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/hsch14/ABC-car_insurance --skill opencode-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-qa
Source: https://github.com/hsch14/ABC-car_insurance/tree/main/.agents/skills/opencode-qa
Command: npx skills add https://github.com/hsch14/ABC-car_insurance --skill opencode-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires opencode, sqlite3, curl, jq, tmux, bun, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a comprehensive, automated suite for verifying the integrity and functionality of the OpenCode coding agent, ensuring that CLI commands, HTTP servers, plugin hooks, and TUI interactions perform as expected.

Core Features & Use Cases

  • CLI & Server Verification: Smoke-test the OpenCode CLI and HTTP server health with isolated, sandboxed environments.
  • Event & Hook Probing: Validate that plugin hooks and SSE event streams fire correctly during agent operations.
  • Session Investigation: Safely query the OpenCode SQLite database to inspect session history, message content, and tool usage without risking data corruption.

Quick Start

Use the opencode-qa skill to run a smoke test on the TUI and verify that the core event stream is functioning correctly.

Frequently Asked Questions about opencode-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I smoke-test the OpenCode agent CLI and HTTP server?

Smoke-test the OpenCode agent by running automated regression checks in an isolated, sandboxed environment to verify CLI commands and HTTP server health. This validates operational integrity without risking your live configuration.

Can I inspect OpenCode session history using SQLite without data corruption?

Yes, you can inspect OpenCode session history using read-only SQLite database queries to safely review message content and tool usage. This diagnostic probe ensures data integrity while investigating agent sessions.

How do I verify OpenCode plugin hooks and SSE event streams are firing correctly?

Verify OpenCode plugin hooks and SSE event streams by probing the agent during operations to confirm they fire correctly. This automated validation ensures your event-driven architecture functions as expected.

Do I need tmux and jq installed to run OpenCode TUI smoke tests?

Yes, you need tmux and jq installed, along with opencode, sqlite3, curl, and bun, to execute TUI smoke tests and regression checks. These dependencies provide the environment required for automated diagnostic probes.

What is the best way to debug an OpenCode agent session that is not responding?

Debug an unresponsive OpenCode agent session by running automated diagnostic probes and querying the SQLite session database. This isolates the failure point by inspecting message content and tool usage safely.

Why does the OpenCode TUI smoke test fail in my environment?

The OpenCode TUI smoke test fails if dependencies like opencode, sqlite3, curl, jq, tmux, or bun are missing or misconfigured. Ensure all required tools are installed and properly set up in your sandboxed environment.