메뉴
Drive one change from implemented to LIVE-VERIFIED and merged — scoped gates, PR, required-checks merge, live-artifact proof, closeout predicates — with no status stalls in between. Use when asked to ship, land, or deliver a change end-to-end.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Judge whether the public PROSE reads professionally — tone, brand-voice, clarity, credibility — and record a content-pinned verdict. Use when DECORVM (the professionalization keeper) queues a "prose changed — re-review voice" finding, or when asked to review/grade how a public README, bio, or positioning doc SOUNDS (not just whether it is spelled right). The deterministic half (spelling, staleness, narrative-accuracy) is scripts/decorum-keeper.py; this skill is its model-in-the-loop voice complement, the sibling of experience-judge.
Connect Antigravity (Agy) to Limen's symmetric peer-conductor protocol. Use when Agy must conduct, execute, review, split, observe, or harvest bounded Limen work through the authenticated conduct CLI or MCP surface.
Score the visual quality of the public surfaces the experience-audit organ captured — layout, typography, coherence, trust — and record verdicts. Use when asked to judge, review, or grade how the public sites/pages LOOK (not just whether they load), or to run the visual half of the experience audit. The mechanical half (reachable/fast/light/no-errors) is scripts/experience-audit.py; this skill is its human/model-in-the-loop visual complement.
Drive a task to a true closeout — ZERO open or dangling items. Verify ground truth read-only across all owners, close every gap so each owner records its own residual work, reach an idempotent fixed point (re-run = no changes), commit all loose work, and produce a relay handoff. Use when asked to close out, finalize, wrap up, archive, or hand off.
Drive a task to a true closeout — ZERO open or dangling items. Verify ground truth read-only across all owners, close every gap so each owner records its own residual work, reach an idempotent fixed point (re-run = no changes), commit all loose work, and produce a relay handoff. Use when asked to close out, finalize, wrap up, archive, or hand off.
| name | ship |
| description | Drive one change from implemented to LIVE-VERIFIED and merged — scoped gates, PR, required-checks merge, live-artifact proof, closeout predicates — with no status stalls in between. Use when asked to ship, land, or deliver a change end-to-end. |
One concern → one branch → merged into main → proven live — executed end-to-end without
pausing to report status (2026-07-04 censor precedent friction-shallow-first; the standing
autonomy grant in CLAUDE.md → Standing Autonomy). This skill COMPOSES the existing machinery —
it introduces no new predicate; every step names the script that owns it.
origin/main,
named by intent (feat/, fix/, heal/, chore/, docs/, refactor/ — CLAUDE.md → Merge &
Branch Protocol). One concern per branch; stage explicitly with git add <path>, never -A.
For a one-file docs append, use scripts/ship-docs.sh <slug> "<msg>" <file…> instead of steps
2-4 — it is this whole skill in one command for the docs class.bash scripts/verify-scoped.sh — it maps changed paths to only
the gates they implicate and names every skipped gate. Fix root-to-leaf and re-run until green.
Never hand-run the full matrix for a scoped diff; never chase a gate the diff doesn't implicate.gh pr create with the green gate run cited in the body.scripts/merge-policy.sh <PR#>:
scripts/await-pr.sh <PR#> --merge (the ONE sanctioned waiter — bounded,
loud, single-instance; never a hand-rolled poll loop).await-pr.sh waits them out within its deadline.
Anything longer belongs to the beat's merge rung (scripts/merge-drain.py via
scripts/drain.sh) — hand off and continue other lanes; never babysit.logs/AUTONOMY_PAUSED first — a merge-prohibiting marker stops this step (await-pr
refuses on its own, but don't even arm it).
Non-deploy verdicts count required checks only; advisory checks never hold a merge.
Website-sensitive PRs require the full rollup green — merging IS the deploy.python3 scripts/ship-gate.py
(reachable deployed URL, from spec/ship-surfaces.json) or the change's own probe
(scripts/probe-runtime-adapter.py, scripts/experience-audit.py, scripts/link-health.py —
whichever owns the surface). If the artifact needs regeneration after merge, regenerate and
push it — the engine merging is not the profile changing.scripts/no-tasks-on-me.sh and scripts/credential-wall.py --check both exit
0; loose work committed; then the relay: what shipped, predicate verdicts as proof, one
registry pointer for anything homed. No caveat tail. For a full session closeout, run
/closeout — this step is its per-change instance.A change is SHIPPED only when: the implicated scoped gates are green, the PR is MERGED via
merge-policy.sh/await-pr.sh, the live artifact is verified (step 5 predicate exit 0 or a cited
probe), and the closeout predicates are green. Merged-but-not-live is NOT shipped — say so
plainly, with the failing probe output.