菜单
Manually resolve a task against the project's context.yaml — shows which domains, components, files, and rules would be injected by the hook. Use for debugging routing and keyword coverage.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oopsla5xx/open-context --skill oc-resolve命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Scan the project and generate a context.yaml draft — reads oc-settings.yaml if present, otherwise infers everything from docs and source code. Runs validate automatically after generation.
First-run setup wizard for open-context — asks 2 questions (scope, communication language), then reads the project's own docs (or source code, if none exist) to synthesize a project profile (stack, architecture, actors) for a single confirm — then generates context.yaml and test phrasing files under .open-context/ (gitignored, local to your machine) and validates in an agentic loop.
Run phrasing coverage tests and amplification safety checks against the project's context.yaml. Reports per-domain pass/fail rates, risk levels, and amplification warnings.
正在显示 SKILL.md
| name | oc-resolve |
| description | Manually resolve a task against the project's context.yaml — shows which domains, components, files, and rules would be injected by the hook. Use for debugging routing and keyword coverage. |
Run the Open:Context resolver for this task and display the full output.
Task: $ARGUMENTS
Locate context.yaml by checking in order:
.open-context/context.yaml in the current working directorycontext.yaml in the current working directorycontext.yaml at the git repository root (traverse up until .git is found)
If OPEN_CONTEXT_FILE is set in the environment, use that path instead.Run:
python3 "${CLAUDE_PLUGIN_ROOT}/src/open_context/cli.py" resolve <task-words> \
--context <path-to-context.yaml>
Pass the task as individual words after resolve (not a single quoted string).
Show the complete output: matched domains, scores, component chain, applicable rules, and resolved files. Include domains that scored below threshold so the user can diagnose why a task didn't match.
If no context.yaml is found, say so clearly and suggest running /oc-setup to generate one.