Commit changes to git

Skill yegor256/courier/skills/commit-changes-to-git

Use this skill when the user wants to commit changes in the working tree of the current Git repository.From its SKILL.md

Install

npx -y skills add yegor256/courier --skill commit-changes-to-git

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

1.4 KB, 274 tokens by cl100k_base, as published. Nobody here has run it

Scope

Operate on Git repository in current working directory. Refuse to bundle unrelated changes into one commit.

Boundaries

Commit files untouched, never reformatting, linting, testing, or building. Honor hooks and signing unless user asked to bypass them. Land one local commit, never amending, rebasing, force-pushing, or pushing.

Staging

Stage only paths user named, or everything when user said so. Refuse to stage secrets. Warn user about skipped secrets instead.

Message

Respect Conventional Commits standard. Prepend ticket number to description with # when user named issue. Derive message from diff and conversation, never from branch name.

Format

Shape commit as type: summary subject, then optional body.

Review

List staged files for user before committing. Show commit subject to user before committing.

Authorship

Limit message to its description. Skip Co-authored-by: trailers, promotional lines, signatures, and emoji. Preserve configured author and committer identity.

Example

User fixes typo in README.md and says "commit it". Stage README.md alone. Write subject docs: fix typo in README. Land one commit carrying that subject.

Done

Confirm one new commit appears after run. Stop after single commit lands.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 274 tokens

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 branchin 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

Derive message from diff and conversation
Show commit subject before committing
Preserve configured author and committer identity
Confirm one new commit appears

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.