Help us improve
Share bugs, ideas, or general feedback.
From go-workflow
Creates git commits with auto-generated conventional commit messages. Analyzes changes via git diff/status, checks branch protection, stages relevant files excluding secrets. Invoke via $commit or 'commit changes'.
npx claudepluginhub gopherguides/gopher-ai --plugin go-workflowHow this skill is triggered — by the user, by Claude, or both
Slash command
/go-workflow:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a git commit with an auto-generated conventional commit message.
Stages, commits, and optionally pushes local changes with a conventional commit message. Analyzes diffs, confirms with user. Automatically creates feature branches on protected branches.
Creates git commits with clear messages from working tree changes, following repo conventions or conventional commits. Handles clean trees and detached HEAD.
Commits git changes with auto-generated message and pushes to origin after analyzing status/diffs, staging specifics, skipping secrets, and warning on main/master branches.
Share bugs, ideas, or general feedback.
Create a git commit with an auto-generated conventional commit message.
$commit
Run these commands to understand the current state:
git status
git diff HEAD
git branch --show-current
git log --oneline -10
Check if you are on main, master, or the default branch:
DEFAULT_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //')
CURRENT=$(git branch --show-current)
If $CURRENT matches the default branch:
Review the diff to understand what changed:
Follow the repository's commit style (check git log --oneline -10).
If the repo uses conventional commits:
<type>(<scope>): <subject>
feat, fix, docs, style, refactor, test, chore, perfStage only relevant files — do not stage secrets (.env, credentials, etc.):
git add <relevant-files>
git commit -m "<type>(<scope>): <subject>"
If there are no changes to commit, inform the user and stop.