opencode-configs

To align OpenCode configuration with official documentation, update rules, commands, and permissions to mirror authoritative sources. This prevents configuration drift and ensures consistent behavior across repository templates, docs, and examples.

OpenCode configuration validation is the process of checking schemas, defaults, and permission rules against official documentation. It enforces consistency with config docs and reduces onboarding effort by synchronizing examples and references.

OpenCode config drift happens when local configuration templates, examples, and references become outdated relative to official documentation. Synchronizing these elements with the latest docs and schemas prevents inconsistent project behavior.

Yes, you can validate OpenCode schemas, defaults, and permission rules across multiple projects. Applying official documentation alignment ensures configuration formats and validation rules remain consistent across repo templates and examples.

The best way to update OpenCode rules and commands is to synchronize them directly with official documentation. Validating schemas and examples against authoritative sources reduces drift and ensures configuration consistency.