opencode-compatibility-audit

Audits repository compatibility against the latest stable opencode-ai release and official OpenCode docs.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/GonkaGate/opencode-setup --skill opencode-compatibility-audit-gonkagate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-compatibility-audit
Source: https://github.com/GonkaGate/opencode-setup/tree/main/.agents/skills/opencode-compatibility-audit
Command: npx skills add https://github.com/GonkaGate/opencode-setup --skill opencode-compatibility-audit-gonkagate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It answers whether the opencode-setup repository still matches the current stable upstream OpenCode contract, catching config, provider, auth, model, or CLI changes that would break the documented GonkaGate setup plan. ## Core Features & Use Cases - Primary-source auditing: Compares npm registry metadata, official OpenCode docs, config schema, tagged source, and CLI help against repository assumptions. - Read-only safety: Runs all inspection in isolated temp directories without touching real user config, auth stores, or login flows. - Structured verdicts: Produces a report classifying findings as compatible, compatible with caveats, or incompatible, separating confirmed upstream changes from inferred risk and prerelease watchlist signals. - Use Case: Before shipping an opencode-setup release, run the audit to verify that the latest opencode-ai stable release still supports the planned provider.gonkagate config, baseURL, and small_model assumptions. ## Quick Start Ask the AI to audit whether this repository is still compatible with the latest stable opencode-ai release and report any breaking upstream changes.

Frequently Asked Questions about opencode-compatibility-audit

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

FAQPage Schema
How do I check if my OpenCode setup is still compatible with the latest release?

Run a compatibility audit comparing your repository's config, provider, and CLI assumptions against the latest stable opencode-ai release from npm and the official OpenCode docs. The audit returns a verdict of compatible, compatible with caveats, or incompatible with cited evidence.

What sources does an OpenCode compatibility audit use?

It uses primary sources only: npm registry metadata for opencode-ai, official docs at opencode.ai, the config schema at opencode.ai/config.json, tagged source and release notes, and isolated CLI help output. Secondary summaries are not used when primary sources exist.

Does the audit modify my OpenCode config or auth files?

No, the audit is strictly read-only. Any CLI inspection runs in a disposable temp directory with HOME, XDG_CONFIG_HOME, XDG_DATA_HOME, and OPENCODE_CONFIG pointed at temp paths, and it never runs login flows or touches real user config.

Does the audit cover prerelease opencode-ai versions?

Prerelease channels like next, alpha, or beta are tracked only as an early-warning watchlist. The main compatibility verdict is based on the latest stable release unless you explicitly ask for prerelease compatibility.

What happens when the audit finds an incompatibility?

The report names the exact repository surfaces that break, cites the confirmed upstream change, and lists minimal recommended fix areas. It does not modify code or design a full migration plan.