What problem does it solve? Publishing a plugin release without testing the actual packed artifact risks shipping crashes or regressions that only appear in the installed tarball, not in the source tree. This Skill provides a repeatable workflow to smoke-test an oh-my-opencode-slim release candidate in an isolated OpenCode environment before public npm publish. ## Core Features & Use Cases - Isolated artifact testing: Builds, packs, and installs the tarball into a throwaway app so validation never depends on the local package cache or source tree. - Environment sanitization: Uses env -i with a temporary HOME and XDG_CONFIG_HOME to strip host variables that could silently add plugins or provider aliases, plus opencode debug config verification of plugin origins. - Crash regression detection: Runs opencode run --print-logs --log-level DEBUG and searches logs for known crash signatures such as the OpenCode 1.17.11 malformed-message TypeError. - Use Case: Before publishing a bugfix release, pack the candidate, install it in a temp directory, run an isolated smoke prompt, confirm no crash signatures appear in logs, and record the results on the release issue using the provided reporting template. ## Quick Start Ask the AI to smoke-test the current oh-my-opencode-slim release candidate by packing it, installing the tarball in an isolated environment, and running an OpenCode smoke prompt.
