opencode-config-validator

Validate OpenCode configuration by checking opencode.json syntax and schema conformance against official standards. The validator returns a deterministic pass or fail result with actionable remediation steps for any detected drift.

Client errors in MCP and LSP typically arise from configuration drift. Validating MCP and LSP server parameters against official specifications catches these deviations early, preventing inconsistent deployments and runtime failures.

Check skill naming and structure by validating that the SKILL.md name matches the slug, verifying proper directory presence, and ensuring frontmatter completeness. This prevents structural errors when adding new skills to your workflow.

Yes, you can use the validator to catch JSON schema drift after modifying opencode.json. It enforces checks on JSON syntax and config schemas, verifying conformance across MCP, LSP, and general opencode usage in development workflows.

Run OpenCode config validation when skills are added, configurations are changed, or validation is explicitly triggered. Running it after modifying opencode.json or adding a new skill catches structural or schema drift early in development.

Yes, the validator checks both skill metadata and tooling configurations. It enforces checks on skill naming and frontmatter completeness while verifying parameters for MCP, LSP server settings, and general opencode.json schema conformance.