菜单
Analyze a project-context problem from `problem`, `target behavior`, and optional `codex session id`; load `project-context-engineer`; propose `minimal`, `systemic`, and `optimal` fixes; wait for explicit choice; then implement it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fix production code for one red Kotlin JUnit case created or aligned by `$code-test-case`; use after that skill when the test is failing and test edits are forbidden.
Review and refactor code after `$code-test-case` and `$fix-red-case` have made a selected case green; use when the user asks to refactor a commit or uncommitted changes before broadening scope.
Convert cases written in `verification-check-format-v0.1` in `full` mode into Kotlin JUnit test code. Use when the input is a verification check artifact with `Feature`, `Rule`, `Example`, `Given`, `When`, `Then`, and `And`.
Design one `verification-check-format-v0.1` full-mode test case from a requirement, bug report, or desired behavior description.
Write or normalize one or more `verification-check-format-v0.1` checks in `full` mode. Use when a user or another skill needs `Feature` / `Rule` / `Example` / `Given` / `When` / `Then` text rendered as concise, contract-based, implementation-light prose.
Review changes in framework context files for conciseness, minimality, task fit, framework integration, ambiguity, actionability, verifiability, contradictions, scope clarity, and non-English text. Use when Codex reviews diffs or changed files in `.agents/`, `src/project-baseline.md`, `src/conventions/`, `src/roles/`, or framework templates.
| name | fix-project-context |
| description | Analyze a project-context problem from `problem`, `target behavior`, and optional `codex session id`; load `project-context-engineer`; propose `minimal`, `systemic`, and `optimal` fixes; wait for explicit choice; then implement it. |
Read framework_checkout_root/src/references/context-fix-minimality.md.
Read framework_checkout_root/src/references/context-fix-workflow.md.
This skill always resolves the role to project-context-engineer.
Before task triage, load framework_checkout_root/src/roles/project-context-engineer.md.
If that file is missing, say so and stop.
Treat editable roots as:
./AGENTS.md./.agents/** outside framework_checkout_root/** and ./devlog/**./.codex/** outside framework_checkout_root/** and ./devlog/**./README.md only when it is an active agent-facing entry point or the narrowest consistent location.If the case is about framework-provided context under framework_checkout_root/src/**, stop and tell the user to use $fix-framework-context.
Work from the smallest relevant project context file set under:
./AGENTS.md./.agents/** outside framework_checkout_root/** and ./devlog/**./.codex/** outside framework_checkout_root/** and ./devlog/**./README.md only when it is agent-facing or already part of the current context flow.Classify each candidate by layer (agents-root | agents-dir | codex-dir | readme | reference).