Stats
Actions
Tags
From python-api
Git commit workflow with enforced conventional commit style. Use when Claude needs to stage and commit changes, craft commit messages, or the user asks to commit, make a commit, or save their work. Ensures consistent commit message format, proper scoping, and atomic commits across the project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/python-api:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Stage and commit changes following conventional commit style and atomic commit principles.
Stage and commit changes following conventional commit style and atomic commit principles.
<type>(<optional scope>): <short summary>
| Type | When to use | Example |
|---|---|---|
feat | New feature or capability | feat: add user authentication flow |
fix | Bug fix | fix: resolve null pointer on empty input |
refactor | Code change that neither fixes a bug nor adds a feature | refactor: extract parser into standalone module |
style | Formatting, whitespace, semicolons — no logic change | style: apply formatter to config files |
docs | Documentation only | docs: add API usage examples to readme |
test | Adding or updating tests | test: add edge case coverage for validator |
chore | Build process, tooling, dependencies, config | chore: update dependency lockfile |
perf | Performance improvement | perf: cache repeated database lookups |
ci | CI/CD pipeline changes | ci: add lint step to PR workflow |
Use scope to narrow context when the type alone is ambiguous. Derive scopes from the project's directory structure or domain areas:
feat(auth): add OAuth2 token refresh
fix(api): handle timeout on large payloads
docs(contributing): add setup instructions
git status and git diff (staged + unstaged) to understand what changedgit log --oneline -10 to match the project's existing commit stylepackage.json scripts, Makefile, or CI config for available commands. Fix any failures before proceeding.git add file1 file2), never git add -A or git add .git status after to confirm the commit succeededFor commits that need a body (rare — prefer concise single-line messages):
<type>(<scope>): <summary>
<body explaining why, not what>
.env, credentials, API keys, or tokens. Warn the user if these are staged..gitignore coverage before staging.--no-verify. If a hook fails, fix the underlying issue.Co-Authored-By: Claude <[email protected]>
# Feature — new capability
feat: add webhook notification system
# Feature with scope
feat(api): add rate limiting middleware
# Fix — bug correction
fix: prevent crash on malformed JSON input
# Style — formatting only
style: apply consistent indentation across modules
# Docs — documentation
docs: add architecture decision records
# Chore — tooling/config
chore: broaden gitignore to cover build artifacts
# Test with scope
test(auth): add integration tests for token refresh
# Refactor with scope
refactor(db): replace raw queries with query builder
npx claudepluginhub cdcoonce/claude-workflow --plugin python-apiManages Git commit workflow using Conventional Commits format with safety protocols. Creates, validates, executes commits; handles hooks, PRs, and safety checks before operations.
Executes git commits with conventional commit message analysis, intelligent staging, and message generation. Use when asked to commit changes or when /commit is invoked.
Creates semantic git commits with conventional commit format, stages changes, and pushes to remote. Handles pre-commit hooks and writes meaningful commit messages.