菜单
Git environment for write-access container agents. Covers the bare repo clone model, branch assignment, auto-push after commit, and branch restrictions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | container-git-write |
| description | Git environment for write-access container agents. Covers the bare repo clone model, branch assignment, auto-push after commit, and branch restrictions. |
ACCESS SCOPE: write-access
You are running inside a Docker container. Your working directory is a git checkout cloned from a bare repo on the host.
You work on a single branch:
docker/{project-id}/{agent-name}
The seed branch is docker/{project-id}/current-root, synced from the exterior (host) repo. Your branch was forked from docker/{project-id}/current-root at launch.
Every git commit you make is automatically pushed to docker/{project-id}/{agent-name} on the bare repo by a PostToolUse hook. You never need to run git push.
git push _it is handled for you.If you attempt git push or git checkout to a different branch, it will be blocked.
You can read any branch without switching:
git show docker/{project-id}/agent-2:path/to/file.ts
git log docker/{project-id}/current-root --oneline -10
git diff HEAD..docker/{project-id}/current-root -- src/
Your branch is visible to the coordination server, the operator, and other agents that fetch it. The bare repo is persistent and survives container restarts.
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.