メニュー
Lint, type-check, commit, and push in one flow. Use when user says /ship or asks to commit+push.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ship |
| description | Lint, type-check, commit, and push in one flow. Use when user says /ship or asks to commit+push. |
Run all steps in order. Stop immediately on any failure.
Before running checks, detect what tooling is available:
package.json exists in the repo root.lint:ci and types scripts inside it.pnpm lint:ci (if script lint:ci is defined)pnpm types (if script types is defined)package.json does not exist or neither script is defined, skip this step entirely and proceed to Step 2.If any executed check fails, show the errors and stop. Do not commit broken code.
Run all three in parallel:
git status
git diff --staged && git diff
git log --oneline -5
If there are no changes to commit, inform the user and stop.
git add -A or git add .Always pull before push to avoid rejection:
git pull --rebase && git push
If rebase has conflicts, show them and stop — let the user decide.
git push --force--no-verify)Audit a React/TSX repository for React anti-patterns by loading rule cards from the brainstormer card library, scanning via each card's declared detect strategy, and filing one grouped GitHub issue per `(skill, rule_id)` via the `gh` CLI. Phase 3 adds the full re-run lifecycle: `findIssueByLabel` lookup, in-place body rewrite bounded by `react-audit:managed:start/end` sentinels (human comments survive), close-with-dated-resolution on emptied findings, regression-with-backlink on resurfaced findings, label-collision protocol under concurrent runs, never-reopen invariant. Phase 2c grouped body (15 MVP cards, per-occurrence severity, `<details>` collapsibles) and Phase 2b smart scan (`SMART_SCAN_THRESHOLD=50`) unchanged. Manual invocation only — no hooks. Triggers on `/react-audit`, "audit this repo for react anti-patterns", "run a react audit". Skip design questions, scaffolding, audits of non-React frameworks (Vue, Svelte, Solid).
Discovery interview and requirements gathering session. Pressure-test an idea, architecture, or design decision through structured client interviews. Use when the user wants to be challenged on their thinking, explore trade-offs, or vet a plan before committing.
Create a Product Requirements Document through structured interview. Use when the user wants to write a PRD, define requirements, or plan a new feature.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Convert a PRD into independently-grabbable GitHub issues using vertical slices. Use when the user wants to create issues from a PRD, break down a PRD into tasks, or create GitHub issues from requirements.
Test-Driven Development workflow using vertical slices. Use when implementing features with TDD, writing tests before code, or doing red-green-refactor cycles.