菜单
Land finished work in a Git repository through Gate, Record, Commit, and Publish. Use when the user asks to close completed work, commit and push it, or open a pull request; use repository review workflows for reviewing an existing PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bootstrap software repositories from live evidence. Use for initial setup, inherited-codebase rehabilitation, repository mapping, conventions, documentation architecture, safe restructuring, or agent-ready tooling.
Solve ambiguous, high-stakes, or multi-variable questions with a labelled problem tree. Use for open-ended life, business, product, strategy, and root-cause reasoning; route concrete feature briefs to $grill-me and specific failures to $debugging.
Diagnose software failures through evidence-based root-cause analysis. Use for bugs, failing tests, runtime errors, data anomalies, stuck jobs, environment failures, and intermittent or expensive-to-reproduce incidents.
Create, edit, and run persistent Codex workflow graphs with optional GitHub delivery.
Turn a rough software feature request into one codebase-grounded implementation brief. Use for feature pitches, vague product requirements, solution exploration, or explicit “grill me” requests before coding; use $brainstorming for non-implementation questions.
Implement an agreed story, plan, or failing-test target and prove the resulting behavior. Use when an accepted contract authorizes production changes; route diagnosis-only work to $debugging and test design to $tdd.
| name | ship |
| description | Land finished work in a Git repository through Gate, Record, Commit, and Publish. Use when the user asks to close completed work, commit and push it, or open a pull request; use repository review workflows for reviewing an existing PR. |
Apply Gate → Record → Commit → Publish. Read playbook.md for repository discovery and command mechanics.
Inspect repository instructions, branch or commit, upstream, dirty state, existing commits, and task records. Discover the repository's actual build, static-check, test, changed-flow verification, and review gates. Run every applicable required gate against the tree that will be shipped.
A red required gate keeps the work in progress. An unavailable required gate becomes a named blocker; an unavailable optional surface becomes a reported limitation.
Complete Gate when each applicable check has a fresh result tied to the intended tree.
Follow the repository's task-record lifecycle. When an active plan or equivalent drove the work, record a factual dated outcome, move it to the repository's completed state, remove only debt resolved by this change, and add a lesson only when the task produced a reusable reasoning rule.
For work already recorded elsewhere, use the existing record and avoid creating empty ceremony. Route durable business-document changes through the repository's documentation-sync process.
Complete Record when the final tree contains an accurate durable account of what landed and what was cut.
Stage only intended implementation and record files. Derive commit style from repository policy and recent history. Recheck the staged diff, then create the minimum coherent commit set authorized by the user.
Complete Commit when committed content equals the gated tree and unrelated working-tree changes remain preserved.
Use the discovery, confirmation, mutation, and idempotency mechanics in playbook.md. Execute only the requested publish actions; commit, push, pull-request, merge, and deploy authority are independent.
Shipping is complete when the requested local commit, pushed branch, or pull request exists at its proved SHA, all gate evidence and limitations are reported, and task records match that tree.
