القائمة
Resolve configuration files through a three-layer override chain (project -> user -> default). Enables customizable skill behavior without editing skill files directly.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Complete Bash development skill — defensive patterns, testing with BATS, linting with ShellCheck, POSIX compatibility, idioms, project structure, and CI/CD integration. Load automatically when working with .sh files.
Python debugging via mcp-dap-server with debugpy. Use when stepping through Python code, finding bugs, inspecting runtime state, or debugging pytest tests.
Complete Python development skill — style, type safety, error handling, testing, async, packaging, and performance. Load automatically when working on Python projects.
uv package manager for Python — project setup, dependency management, lockfiles, and migration from pip/poetry/pipenv. Use when setting up Python projects, managing dependencies with uv, or migrating from pip/poetry/pipenv.
Packer HCL2 template authoring. Load when working with .pkr.hcl files. Covers template syntax (variable/locals/source/build blocks), HCL2 type system, provisioners, post-processors, and template organization patterns.
Infrastructure and CI/CD around Packer VM builds. Covers HCP Packer Registry integration, artifact management, automated build pipelines, multi-platform orchestration, image versioning and rollout strategies.
| name | resolution-chain |
| description | Resolve configuration files through a three-layer override chain (project -> user -> default). Enables customizable skill behavior without editing skill files directly. |
| when_to_use | When loading configuration files, custom rules, or overrides for any skill or command. When the user wants to customize behavior per project. NOT for runtime data — for configuration only. |
| allowed-tools | Read, Bash, Grep |
| effort | low |
First-found-wins configuration resolution. Customize without editing skills.
The resolution chain enables users to override any configuration file at three levels:
1. <cwd>/.opencode/<file> # Project-level override
2. ~/.config/opencode/<file> # User-level override
3. <skill-root>/references/<file> # Bundled default
Rules:
scripts/resolve-file.sh <relative-path> [data-dir]
Returns the first file found in:
.opencode/<path> (project override)<data-dir>/<path> (user override)<skill-root>/references/<path> (bundled default)scripts/resolve-rules.sh <filename> [data-dir]
Returns the first file found in:
.opencode/<filename> (project override)<data-dir>/<filename> (user override)Skills load custom rules via:
# Load project-specific planning rules
RULES=$(bash scripts/resolve-rules.sh planning-rules.md ~/.config/opencode)
if [ -n "$RULES" ]; then
echo "Loaded custom planning rules"
echo "$RULES"
fi
Commands load rules at startup:
# In commands/plan.md:
1. Resolve custom rules: resolve-rules.sh planning-rules.md
2. If rules found: append as additional instructions
3. Execute command with merged instructions
User creates: my-project/.opencode/planning-rules.md
Content: "Always use PostgreSQL, never SQLite"
When /plan runs:
1. resolve-rules.sh checks:
-> my-project/.opencode/planning-rules.md? YES -> return content
-> ~/.config/opencode/planning-rules.md? SKIP (first-found-wins)
2. Plan generator APPENDS custom rules as additional instructions
[Check] Resolution order: project -> user -> default [Check] Empty files treated as absent [Check] First-found-wins, never merged [Check] resolve-rules.sh always exits 0 (non-fatal if no rules found)