菜单
Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact delivery. Do not use outside a Git repository or to publish a formal Release without explicit authorization.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | github-delivery |
| description | Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact delivery. Do not use outside a Git repository or to publish a formal Release without explicit authorization. |
Deliver only the verified, authorized scope.
references/git-delivery-policy.md.Do not change remotes or credentials to make push succeed. Git push, artifact upload, draft Release, formal Release, and registry publication are separate authorizations.
Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md.
Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.
Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.
Use when the current host has dated WRITE_SUBAGENT: VERIFIED evidence and the user requests parent-supervised native-subagent TDD for one workstream task.
Use when a declared frontend, backend, or integration workstream has one READY task for parent-led sequential TDD.
Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records.