agentsclimarketplace

Git commits

Skill dilhanz/ship/skills/git-commits

Use when making git commits during Ship feature builds — provides atomic commit format and conventionsFrom its SKILL.md

Install
npx -y skills add dilhanz/ship --skill git-commits

Assembled 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

  1. Stage specific files — never git add . or git add -A. List exact files changed.
  2. One task = one commit — do not batch multiple tasks into one commit.
  3. Commit only after verify passes — the verify command in the task must succeed before committing.
  4. 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"

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.