Commit

Skill skrrt-sh/skills/skills/ship/commit

Create focused conventional commits with a mandatory gitmoji. Use when the user asks to commit, write a commit message, or split changes into commits.From its SKILL.md

Install

npx -y skills add skrrt-sh/skills --skill commit

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

2 stars2 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

2.4 KB, as published. Nobody here has run it

Commit Changes

Create the smallest coherent commits that explain what changed and why.

Format

type(scope): :gitmoji: imperative subject

body explaining what changed and why

footer

Use a standard conventional-commit type and gitmoji code.
Put the gitmoji immediately after type(scope):; omit an uncertain scope.
Include a body for every commit.
Add BREAKING CHANGE: only for a real breaking change.
Add issue footers only for issues the user or repository identifies.
End with Co-Authored-By: Skrrt Bot <[email protected]> unless the user opts out.

Process

Read .agents/ship.md at the repository root. If missing, stop and ask the user to run /setup.
Inspect git status --short, staged and unstaged diffs, and the current branch. Do not include unrelated files without approval.
Protect work on a forbidden branch before staging: create a correctly named work branch from the current HEAD with git switch -c <type>/<description>. Do not pull, switch bases, or stash first; the new branch must retain the current worktree exactly.
If this is a fix to a recent PR or MR, read references/follow-up.md before staging.
Group the diff by intent. If a type and gitmoji disagree, split the change instead of forcing a message.
Stage only the intended files or hunks. Review git diff --cached before each commit.
Write the message to a mktemp file outside the repository, commit with git commit --file <file>, then remove it. A fixed path is unsafe: a second agent, or your own next commit, can overwrite the message between writing it and committing, which silently ships a message describing the wrong diff.
Verify the resulting commit and report its hash, subject, included files, and known test status.

Guardrails

Commit only when the user asked for a commit; loading this skill is not that request.
Follow the protected branches and work base in .agents/ship.md.
Preserve unrelated and untracked work.
Never invent test results, amend, rewrite history, or force-push unless explicitly requested.
Never commit secrets or likely credential files; stop and warn the user.

What ships with it: 2 files

1.5 KB alongside SKILL.md

evals/

commit-basic.json418 B
trigger-evals.json1.1 KB

Gives 1 of the 12 instructions most pr commit review skills give

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchhere, and in 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Read ship configuration file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.