Menú
Use when making git commits during Ship feature builds — provides atomic commit format and conventions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when a feature plan has been verified and is ready for implementation — executes tasks with atomic commits
Use when you want to auto-run all remaining Ship steps for a feature without manual step-by-step invocation
Use when a feature has been brainstormed and needs a detailed implementation plan with tasks
Use when a brainstormed feature needs architectural decisions — presents 2-3 approaches for user to choose before planning
Use when a plan has been created and needs independent verification against codebase patterns before building
Use when beginning new feature work, adding functionality, or fixing a bug — runs intensive brainstorming to capture requirements before planning
| name | ship:git-commits |
| description | Use when making git commits during Ship feature builds — provides atomic commit format and conventions |
| effort | medium |
| user-invocable | false |
Ship uses atomic commits — one commit per completed task.
<type>(<feature-name>): <description>
<type> — one of: feat, fix, refactor, test, docs, chore<feature-name> — the feature slug from .planning/features/{name}/<description> — imperative, present tense, lowercase, no period, under 60 charsfeat(user-auth): add user model with prisma schema
feat(user-auth): implement bcrypt password hashing
fix(user-auth): handle expired token edge case
test(user-auth): add unit tests for auth service
refactor(user-auth): extract email validation helper
chore(user-auth): install bcrypt and jsonwebtoken
git add . or git add -A. List exact files changed.git add <file1> <file2> ...
git commit -m "feat(feature-name): description of what was done"