القائمة
Git environment for read-only container agents (reviewers, planners). Covers the bare repo clone model and read-only workspace constraints.
التثبيت باستخدام 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-readonly |
| description | Git environment for read-only container agents (reviewers, planners). Covers the bare repo clone model and read-only workspace constraints. |
ACCESS SCOPE: read-only
You are running inside a Docker container. Your working directory is a git checkout cloned from a bare repo on the host. Your workspace is read-only _no changes you make will persist.
You start on docker/{project-id}/{agent-name}, which contains the code you are reviewing or analysing. You can freely navigate git history and read any branch.
git show docker/{project-id}/agent-2:path/to/file.ts
git log docker/{project-id}/current-root --oneline -10
git diff docker/{project-id}/current-root..docker/{project-id}/agent-1 -- src/
You do not write code, create commits, or modify files. If you spot something that needs changing, report it in your output _do not fix it yourself.