메뉴
Run the full end-to-end cadence to finish a slice of SelfOS work — quality gate, self code-review, doc sync, and a Conventional Commit. Use when the user says "ship it", "finish this slice", "wrap up", or when an implementation slice is code-complete and ready to land.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Persist user feedback, corrections, or durable preferences into the project's config so they aren't forgotten. Use whenever the user corrects your approach, states a standing preference ("from now on…", "always/never…"), or makes a decision that should outlive this session. The reactive half of SelfOS's living-docs loop.
Create a Conventional Commit for SelfOS with the required co-author trailer, after verifying the quality gate passes. Use when the user asks to "commit", or as the final step of shipping a slice. Refuses to commit on main or when checks are failing.
Run the automatable subset of SelfOS's Definition of Done (typecheck, lint, format check, unit tests, and E2E when present) and report pass/fail. Use before committing, before declaring a slice done, or when the user asks to "run the checks / quality gate / verify it's clean".
After code changes, detect drift between the code and the docs (docs/specs/, CLAUDE.md, skills) and propose the concrete edits to bring them back in lockstep. Use as part of finishing a slice, before committing, or when the user asks to "update the docs / sync the spec / check the docs are current". The proactive half of SelfOS's living-docs loop.
Scaffold or revise a SelfOS feature-set spec in docs/specs/. Use when starting a new feature set, when the user asks to "write/draft a spec", or before writing any feature code (spec-driven workflow). Produces a doc that follows _TEMPLATE.md.
| name | ship-slice |
| description | Run the full end-to-end cadence to finish a slice of SelfOS work — quality gate, self code-review, doc sync, and a Conventional Commit. Use when the user says "ship it", "finish this slice", "wrap up", or when an implementation slice is code-complete and ready to land. |
Orchestrates SelfOS's Definition of Done so a slice lands clean. Run only when the work is code-complete (implementation + tests written).
<type>/<slug> branch off main, not main itself. (If you're on
main, branch first — main is only ever updated via a merged PR.)quality-gate. Run it. Fix any failures before continuing. (typecheck · lint · format · unit
tests · E2E when present.)code-reviewer agent on git diff main...HEAD. Address
every finding, or explicitly note why one is accepted. Re-run quality-gate if you changed code.sync-docs. Detect and apply doc/spec/skill drift (via the doc-auditor agent). Update the
CLAUDE.md Changelog if a rule changed.commit. Create the Conventional Commit(s) with the co-author trailer (on the branch).git push -u origin HEAD then gh pr create with a Conventional Commit title (this
title becomes the squash commit on main, so it drives the changelog + version bump). Wait for CI to go
green.gh pr merge --squash --delete-branch. main now has one clean commit. Never push to
main directly or merge locally; never git merge origin/main into a branch (rebase onto it).main, ask the user: "Tag & publish vX.Y.Z now, or batch with the
next change?" If yes, run the release skill. (A docs:/chore:/test:-only slice cuts no release —
say so.)main moves only through a merged PR — never a direct push or a local merge.