메뉴
Implement a piece of work based on a spec or set of tickets.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run one scheduled cloud-routine fire: pick the oldest open `ready-for-agent` issue, drive it to a merge-ready PR, and STOP at the merge gate without merging. Composes `ship`. Use only when running the scheduled cloud ship routine for Gharib89/crm (the routine prompt invokes this skill by name); not for an interactive `/ship`.
Review inbound agent-shipped PRs at the merge gate — drift checklist, targeted live e2e, fix-in-place, review-bot iteration (Copilot + CodeRabbit) — leaving each PR merge-confident (gate-passed) or explicitly failed (gate-failed).
Take a tracker issue to a merge-ready PR in one unattended run, stopping only at a human merge gate. Composes the `tdd` and `code-review` skills. Use when the user wants to ship an issue or take an issue through to a PR; also invoked by the cloud ship routine.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
| name | implement |
| description | Implement a piece of work based on a spec or set of tickets. |
| disable-model-invocation | true |
| metadata | {"internal":true} |
Implement the work described by the user in the spec or tickets.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, use /code-review to review the work.
Commit your work to the current branch.
