agentsclimarketplace

Git commit batch

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

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

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

{{ 𝚫𝚫𝚫 }} Split uncommitted changes into granular commits.

SKILL.md

2.1 KB, 411 tokens by cl100k_base, as published. Nobody here has run it

Current state

git status --short
git diff --stat HEAD

Steps

  1. The current state above was captured at invocation; run git diff HEAD on specific files only where the stat alone can't tell you what a change is.
  2. Analyse the changes and group them into logical commit units — each group should represent a single coherent change (e.g. one feature, one fix, one refactor).
  3. Present the proposed commit plan as a numbered list:
    • Group name / files involved
    • Suggested commit message (conventional commits format)
  4. Await approval — stop here and do not proceed until the user responds:
    • If approved, execute commits sequentially. For each group:
      1. Stage only the files listed for that group (git add <files>)
      2. Commit with the proposed message
      3. Confirm success before moving to the next group
    • If changes requested, revise the plan and repeat from step 3.
  5. After all commits, push to upstream.

Grouping Guidelines

  • Prefer smaller, atomic commits over large ones
  • Keep unrelated changes in separate commits even if they touch the same area
  • Config/dependency changes separate from feature code
  • Test changes alongside the code they test (same commit), unless the test is independent
  • Generated files (lockfiles, build artefacts) get their own commit if significant
<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>

Keep looking

Skills are one crate of 328,083. 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.