一键导入
ship
Ship - Commit and Push in one command. Chains staging, conventional commit, and push. Checks quality gates before any commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Ship - Commit and Push in one command. Chains staging, conventional commit, and push. Checks quality gates before any commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit naming quality (files, functions, types, variables, folders) without reading the code. Takes names as input and reports what Claude understands from each name alone. Judges three axes: Screaming Architecture (does the name reveal the domain?), Clean Code (full words, intention-revealing, no abbreviations), and Ubiquitous Language (vocabulary consistency across the codebase). Useful to validate that names self-document.
Extracts business rules from a module (backend + frontend) and produces three tables: Product view (business concepts), Backend dev view (type + source), Frontend dev view (type + source). Saves to docs/business-rules/.
Strategic DDD guide for this project (fullstack — backend + frontend share the same bounded contexts). Use to slice the domain into bounded contexts, define ubiquitous language, create a new business module, analyze boundaries between contexts. Tactical patterns follow Clean Architecture (see architecture-backend and architecture-frontend skills).
Runs a Big Picture Event Storming session on a bounded context or the entire codebase (backend + frontend). Discovers domain events, commands, entities, context boundaries, frontend projections (hooks, presenters, views). Produces a structured document in docs/ddd/.
Autonomous frontend feature implementation via spec-driven development. Orchestrates a frontend-planner and a frontend-implementer with architecture-frontend preloaded. Applies Humble Object pattern to views, MVVM structure with Presenter classes + Zod ViewModels, singleton registry DI. Consumes specs produced by /product-manager. For backend features, use /implement-feature instead.
Feature challenge and specification. Use to define a feature, write acceptance criteria, scope a ticket, produce INVEST specs with custom DSL in docs/specs/. Refuses vague scopes and forces clarification.
| name | ship |
| description | Ship - Commit and Push in one command. Chains staging, conventional commit, and push. Checks quality gates before any commit. |
| triggers | ["ship","/ship","commit.*push","push"] |
This skill is activated with /ship. It chains verification, commit, and push.
/ship # Commit + push
/ship no-push # Commit only, no push
BEFORE any commit, run:
pnpm test
If tests fail: display the errors and STOP. Do not commit until all tests pass.
git status --short
git branch --show-current
git log --oneline -5
Guards:
main: STOP, refuse to push directly.env, credentials, or secretsgit add <specific files> (not git add -A)Infer the message from the changes:
<type>(<scope>): <description>
| Type | Usage |
|---|---|
feat | New feature |
fix | Bug fix |
refactor | Refactoring |
test | Tests only |
chore | Maintenance |
Rules:
no-push)git push origin <branch>
SHIP
Branch : <branch>
Commit : <type>(<scope>): <description>
Push : origin/<branch>
Tests : all green
--force pushmain--no-verify