بنقرة واحدة
opencode-config
Working on config and plugins for opencode
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Working on config and plugins for opencode
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Work inside a running marimo notebook's kernel — execute code, create cells, and build a notebook as an artifact. Use when the user wants to start a marimo notebook or work in an active marimo session.
Hypothesis-driven debugging methodology: systematic investigation, binary search isolation, escalation criteria. Load when debugging complex, elusive, or multi-system bugs.
Systematic code refactoring methodology using ast-grep, comby, and manual transformations. Load when performing large-scale code restructuring or systematic transformations.
Deep research methodology: recursive exploration, branch-and-synthesize pattern, documentation structure. Load when conducting broad, open-ended research on technical or scientific topics.
Code review framework: 5-category evaluation, structured output format, severity levels. Load when performing thorough code reviews of changes, diffs, or pull requests.
Software development workflow patterns: exploration, implementation, testing, review cycles. Load this skill when coordinating multi-step development tasks or delegating software work.
| name | opencode-config |
| description | Working on config and plugins for opencode |
Global config in ~/.config/opencode and project-local config in ./.opencode
Opencode source code is
command_tutorial.md describes creating commands in opencode
.opencodeThe project-local .opencode/ directory is discovered by walking up from the current directory to the worktree root, finding every ancestor with a .opencode folder. All discovered directories contribute to a combined config layer (with later/higher precedence in some cases).
| File | What it configures |
|---|---|
opencode.json / .jsonc | Main project configuration (merged from all .opencode dirs) |
tui.json / .jsonc | TUI-specific settings: keybindings, theme preferences |
| Directory | Contents |
|---|---|
agent/ or agents/ | Custom agent definitions (*.md) |
command/ or commands/ | Custom slash commands (*.md) |
plugin/ or plugins/ | Local plugins (*.ts / .js) |
mode/ or modes/ | Mode definitions (*.md) |
themes/ | Custom TUI themes (*.json) |
plans/ | Session plan files (*.md) — auto-generated (VCS-backed projects only) |
bin/ | Installation binaries (managed by the installer) |
AGENTS.md — Project-level instructions injected into agent prompts (can also live at any ancestor directory, not just .opencode)CONTEXT.md / CLAUDE.md — Also discovered as instruction files up the tree| Flag | Effect |
|---|---|
OPENCODE_CONFIG_DIR | Override base config directory path |
OPENCODE_CONFIG | Point to a specific opencode.json file |
OPENCODE_TUI_CONFIG | Point to a specific tui.json file |
OPENCODE_DISABLE_PROJECT_CONFIG | Skip all project-local .opencode discovery entirely |
Config directories are collected in this order (later = higher precedence in merge):
~/.config/opencode).opencode dirs (walked up from cwd → worktree).opencode (~/.opencode)OPENCODE_CONFIG_DIR env var overrideWithin the project-local chain, the deepest .opencode (closest to cwd) has highest precedence. Multiple nested .opencode dirs (e.g., monorepo + subproject) are all merged.