skills/jb-committer/SKILL.md
Use when the user asks to commit, commit-current, commit-only, group git changes, or draft commit messages.
npx skillsauth add bjesuiter/skills jb-committerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Author: bjesuiter
Use this skill when the user asks to create commits or commit the current change set.
Read all uncommitted changes in the git working directory: unstaged, staged, and untracked.
Group them by logical change, for example:
Commit all related changes together. Make multiple commits if needed. Choose a clear message that describes the semantic meaning of the change. After finishing the commit(s), always push to the remote.
When using "beans" for ticketing and issue tracking
Sometimes the user wants to only commit files related to a single change. If the user asks for "commit-current" or "commit-only", find all files related to the current change in the chat session and only commit those files as described above. Do not write or commit unrelated change files. After creating the commit, always push to the remote.
Input: "commit-current" Output: Stage only files related to the current change and create a single commit with a concise message.
testing
Use when the user mentions Clawpatch/clawpatch.ai, semantic feature review, repo-wide AI audit, persistent findings, or clawpatch init/map/review/report/fix/revalidate.
development
Use when the user asks for autoreview, Codex/Claude second-model review, or final review of dirty changes, a branch, commit, or PR before ship.
testing
Use when the user asks to cut, prepare, publish, tag, or verify a release, especially npm/package releases.
tools
Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher.