菜单
Use for any agent running inside a Docker container that interacts with the project's git repository. Explains the bare repo clone model, branch naming, and how work is persisted.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for any container agent that posts progress to the coordination server's message board. Defines the curl format, channels, message types, payload conventions, posting responsibilities, and verbosity levels.
Use when a review agent must produce structured output. Defines the BLOCKING/NOTE/Summary/Verdict template, the two-tier confidence rubric, and the JSON shadow block consumed by POST /tasks/:id/reviews. Compose with review-process and a domain skill.
Use when an agent evaluates the output of other agents or decides whether work meets the bar. Enforces rigorous quality standards — reject shortcuts, demand evidence, no rubber-stamping.
Use when an agent is the FSM arbitrator on a durable task. Defines the two triggers, the three ruling types, the POST contract, the addendum-file rules for contradiction rulings, and the 409 handling. Project-agnostic.
Tells container agents where the Unreal Engine source tree is mounted inside the container, so they can grep and read engine headers to verify API signatures and class hierarchies.
Use when an agent must review code changes. Defines the universal review sequence — identify files, read context, check against domain criteria, score, filter. Compose with a domain skill and review-output-schema.
| name | container-git-environment |
| description | Use for any agent running inside a Docker container that interacts with the project's git repository. Explains the bare repo clone model, branch naming, and how work is persisted. |
Containers interact with a bare git repository on the host. This skill describes the git data flow.
Each container agent works on its own branch:
docker/{project-id}/{agent-name}
The seed branch is docker/{project-id}/current-root, which is synced from the exterior (host) repo. Agent branches fork from docker/{project-id}/current-root on first launch.
The container's entrypoint clones from the bare repo at startup. Your working directory is a normal git checkout of your agent's branch.
Your access scope determines how commits reach the bare repo:
Write agents: Every git commit is automatically pushed to docker/{project-id}/{agent-name} on the bare repo. You never need to run git push — a PostToolUse hook handles it. Branch switching is blocked — you stay on your assigned branch.
Build intercept agents (UE): The build hook commits and pushes your changes before routing the build to the host. Manual git push is blocked. Branch switching is blocked.
Read-only agents: Your workspace is ephemeral. No changes persist. You can freely switch branches and navigate git history.
All agents can read any branch without switching:
git show docker/{project-id}/agent-2:Source/MyFile.cpp
git log docker/{project-id}/current-root --oneline -10
git diff HEAD..docker/{project-id}/current-root -- Source/
setup.sh, never recreated on launch.