Stats
Actions
Tags
From git
Commits staged and unstaged changes to git with a concise conventional commit message. Use when changes are ready to be committed, after completing a task, or when the user asks to commit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git:commithaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Stage all changes and commit them with a concise conventional commit message.
Stage all changes and commit them with a concise conventional commit message.
$ARGUMENTS
Before staging files, ensure you are at the repository root:
git rev-parse --show-toplevel
Change to this directory if not already there.
Important: Always run from the repository root to ensure all changes are included.
git add .
Check the staged changes:
git diff --cached --stat
Commit with a concise message following conventional commit guidelines.
Format: type: description (keep under 50 characters)
Common types:
feat: new featurefix: bug fixrefactor: code refactoringdocs: documentationstyle: formatting/styletest: testschore: maintenanceStyle:
Examples:
feat: add user login validationfix: resolve memory leak in parserrefactor: simplify authentication logicIf pre-commit hooks fail:
git add .NEVER use --no-verify or force a commit without resolving issues.
After committing, verify the commit was created:
git log -1 --oneline
npx claudepluginhub langadventurellc/claude-marketplace --plugin gitCreates semantic git commits with conventional commit format, stages changes, and pushes to remote. Handles pre-commit hooks and writes meaningful commit messages.
Creates git commits matching repository style. Stages files explicitly and writes concise commit messages in imperative mood.
Stages files safely avoiding sensitive ones, infers conventional commit type from git diff, drafts message with scope, and executes after confirmation. Use anytime like post-planning or mid-TDD.