메뉴
Use when planning, reviewing, or executing governed ZOB commit/autocommit/autopush behavior through explicit /zcommit commands or the agent-executable zob_zcommit_run tool.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | zob-commit |
| description | Use when planning, reviewing, or executing governed ZOB commit/autocommit/autopush behavior through explicit /zcommit commands or the agent-executable zob_zcommit_run tool. |
This skill defines the easy governed commit workflow for ZOB agents. The /zcommit runtime command and zob_zcommit_run tool prioritize quick, beautiful Conventional Commits over strict per-session ownership tracking: when the user explicitly asks for commit/push, the assistant should use zob_zcommit_run instead of asking the user to paste slash commands. Direct git commit/push/tag remains forbidden.
Baseline safety remains: do not commit, tag, or push unless the user explicitly asks or /zcommit autocommit on / /zcommit autopush on authorizes it for the current repo/session scope.
Use only these explicit commands/tools. Do not invent aliases, shortcuts, shell fallbacks, or alternate command names.
/zcommit status [paths/globs...]/zcommit plan [paths/globs...]/zcommit adopt <paths...>/zcommit commit [paths/globs...]/zcommit push/zcommit autocommit on/zcommit autocommit off/zcommit autopush on/zcommit autopush offzob_zcommit_run tool with action=plan|commit|push|commit_and_pushgit commit, git push, git tag, force push, git add ., or git add -A./zcommit adopt for root/global/broad directory/wildcard adoption; it is an advanced metadata-only ownership hint and should not be needed in normal easy mode./zcommit ... on toggle is active for the current repo/session scope./zcommit commit..pi/git-policy.json and this skill before any governed commit/push work.zob_zcommit_run; do not answer with instructions for the user to run /zcommit manually./zcommit status [paths/globs...] or /zcommit plan [paths/globs...] when the human wants an interactive command, or zob_zcommit_run action=plan when the agent needs a plan without staging./zcommit adopt: /zcommit plan and zob_zcommit_run select all dirty workspace files that pass forbidden-path filtering. When you need “only these session files”, use zob_zcommit_run scope=session_modified, or pass explicit repo-relative files, directories, or globs directly to /zcommit plan and /zcommit commit./zcommit adopt <paths...> only as an advanced metadata hint for strict/legacy flows; it remains metadata-only and does not stage./zcommit plan [paths/globs...] / zob_zcommit_run action=plan produces:
/zcommit commit [paths/globs...] and zob_zcommit_run action=commit|commit_and_push stage only the selected safe paths with git add -- <paths>, never git add . or git add -A, then create the Conventional Commit. Advisory validation failures are recorded in the commit body instead of blocking easy-mode commit./zcommit push or zob_zcommit_run action=push|commit_and_push when push is explicitly requested, the branch/remote are allowed, the commit was created by the zcommit engine, HEAD still equals that commit, and there are no no-ship blockers. Push is not blocked by advisory validation by default.Use Conventional Commits:
<type>(<scope>): <imperative summary>
<body with validation evidence and risk notes when useful>
Allowed default types: feat, fix, docs, test, refactor, chore, ci, build, perf, revert.
Examples:
docs(commit): add governed zcommit policyfix(coms): preserve live delivery guardautocommit defaults to off.autopush defaults to off./zcommit autocommit on authorizes the assistant to create an easy Conventional Commit automatically at assistant message end when safe workspace changes exist./zcommit autopush on remains separate and requires autocommit to be on first.A governed easy commit may include all dirty workspace files that pass forbidden-path filtering, or a narrower explicit subset when pathspecs are passed to /zcommit plan / /zcommit commit. Pathspecs can be repo-relative files, directories, or globs such as .pi/skills/zob-*/SKILL.md. The policy should exclude secrets, credentials, generated/runtime ledgers, sessions, logs, temporary files, vendor folders, and build outputs. /zcommit commit still stages explicit selected paths only; it never stages the entire workspace through git add . or git add -A.
Use when reviewing or modifying ZOB communication, ledgers, Mission Control coms, or live transport safety gates.
Use when an active ZOB handoff, live peer question, required-local coms delivery, or orchestration message is needed.
Use when planning, using, reviewing, or implementing ZOB /goal-linked TODOs, subtodos, TODO HUD progress, delegated TODO claims, or hierarchical subagent work graphs.
Use when working inside the ZOB Pi harness, designing agentic workflows, creating specialist prompts, adding Pi extensions, or turning repeated tasks into software factories.
Use before non-trivial work, uncertain tool selection, orchestration, delegation, context lookup, factory work, autonomous-runtime claims, or evidence-gated completion.
Use when driving the append-only metadata-only worklist blackboard — appending events, reading derived directives, leasing/satisfying directives by content hash, delivering idempotent DIRECTIVE_READY notifications, running the liveness watchdog (observe/escalate), or building/querying the dependency DAG.