Stats
Actions
Tags
From badi
Helps create conventional commits by analyzing staged changes, suggesting type/scope/message, then validates and commits.
How this command is triggered — by the user, by Claude, or both
Slash command
/badi:conv-commitcommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
Conventional commit helper command. Reads staged files, suggests type/scope/message, and validates. # Required Tools - Bash (badi commit command invocation) - git # Procedure ### Step 1: Read the Staged Changes ### Step 2: Type Selection By the nature of the change: - **feat**: A new user-facing feature - **fix**: An existing bug fixed - **refactor**: Behavior unchanged, restructuring (rename, extract) - **perf**: A measured performance improvement - **docs**: Markdown/comment-only changes - **test**: Test files only - **chore**: Maintenance, config, dependencies - **ci**: `.github/wo...
Conventional commit helper command. Reads staged files, suggests type/scope/message, and validates.
git diff --cached --stat
git diff --cached | head -100
By the nature of the change:
.github/workflows etc.The affected area: auth, api, ui, db, config, a module name, etc.
Rules:
# Guidance only
badi commit
# Conventional-format validation + commit
badi commit --message "feat(auth): add JWT refresh tokens"
# Lint check on the last commit
badi commit --check
For complex changes:
feat(auth): add JWT refresh tokens
1h + refresh pattern instead of a 15-minute expiry.
Offline support for mobile clients.
Closes #123
BREAKING CHANGE: use tokens.access instead of access_token
/conv-commit
npx claudepluginhub fatihkan/badi --plugin badi