Git commits
Use when making git commits during Ship feature builds — provides atomic commit format and conventionsFrom its SKILL.md
npx -y skills add dilhanz/ship --skill git-commitsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
Git Commit Conventions
Ship uses atomic commits — one commit per completed task.
Format
<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 chars
Examples
feat(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
Rules
- Stage specific files — never
git add .orgit add -A. List exact files changed. - One task = one commit — do not batch multiple tasks into one commit.
- Commit only after verify passes — the verify command in the task must succeed before committing.
- No WIP commits — every commit on main represents working, verified code.
Command Template
git add <file1> <file2> ...
git commit -m "feat(feature-name): description of what was done"