OpenCode Config

A personal OpenCode setup for planning, building, and reviewing software with a consistent and safety-focused workflow.

Use this repository as a ready-to-use global configuration or as a starting point for your own setup.

What You Get

• Guided workflows for requests from discovery through delivery.
• Reusable commands for plans, reviews, pull requests, releases, and more.
• Skills for research, testing, delivery, and documentation.
• Safe defaults for file changes, shell commands, and local secrets.

Quick Start

1. Install OpenCode.

2. Clone this repository to OpenCode's global configuration directory (backup your own settings first!!):

   git clone https://github.com/joaomj/opencode.git ~/.config/opencode

3. Start OpenCode in any project:

   opencode

If ~/.config/opencode already contains your configuration, back it up before you clone this repository.

Restart OpenCode after you change opencode.jsonc, plugins, commands, or skills.

Archived skills remain under archive/skills/ for local recovery and are not loaded by OpenCode.

Policy Plugin

The policy gate (plugins/policy-gate.ts) enforces workflow ownership, approval, and verification. OPENCODE_PURE=1 is blocked.

• Check health: bun scripts/verify-policy.ts
• Guarded launch: bash scripts/launch-opencode.sh
• Narrow self-repair (no PURE): OPENCODE_POLICY_REPAIR=1 opencode or approve policy-self-repair for plugins/policy-gate.ts, opencode.jsonc, and related policy files. PURE is not required to fix the plugin itself.

Releases

Use semantic version tags for releases:

• Increase the patch number for backward-compatible fixes.
• Increase the minor number for backward-compatible features.
• Increase the major number when command, skill, or permission behavior breaks.

Use /release <version> to publish a user-approved GitHub release with GitHub-generated release notes.

Disclaimer

This is a personal configuration. It is not built by the OpenCode team and is not affiliated with OpenCode or Anomaly.

License

MIT