Git commit one

Skill JasonWarrenUK/goblin-mode/skills/git-commit-one

Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.

Install

npx -y skills add JasonWarrenUK/goblin-mode --skill git-commit-one

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
5 stars5 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.

What its author says it does

Copied from the file, not written here

{{ 𝚫𝚫𝚫 }} Generate a commit message. If nothing staged, stage all changes.

SKILL.md

1.1 KB, 200 tokens by cl100k_base, as published. Nobody here has run it

Current state

git status --short
git diff --cached --stat

Steps

Per the state above: if no changes staged, stage all. If files are already staged, do not stage more files.
Generate commit message per conventional commits format.
Show message and await approval:
- If approved, push to upstream
- If changes requested, revise and repeat

<template format-reference="https://www.conventionalcommits.org/en/v1.0.0/"> `type(scope?): description\n\nbody (optional)\n\nBREAKING CHANGE: footer (if applicable)` </template> <conventions> - Subject line: imperative mood, lowercase, no period, max 50 chars (`add feature` not `added feature` or `adds feature`) - Body: explain *what* and *why*, not *how*; wrap at 72 chars </conventions>

Gives 2 of the 12 instructions most pr commit review skills give in 200 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formatin 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linehere, and in 50 of 888, across 41 files
use imperative mood in commit messagesin 45 of 888
generate a conventional commit messagehere, and in 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

do not stage more files if files are already staged
show message and await approval
revise message if changes are requested

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.