Stats
Actions
Tags
From dev-kit
This command helps you create well-formatted commits following the Conventional Commits specification.
How this command is triggered — by the user, by Claude, or both
Slash command
/dev-kit:commitFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Claude Command: Commit This command helps you create well-formatted commits following the Conventional Commits specification. ## Usage Basic usage: With options: ## Command Options - `--no-verify`: Skip pre-commit checks (lint, build, etc.) - `--style=simple|full`: - `simple` (default): Creates concise single-line commit messages - `full`: Creates detailed commit messages with body and footer sections - `--type=<type>`: Specify the commit type (overrides automatic detection) ## What This Command Does 1. **Pre-commit checks** (unless `--no-verify`): - Lint (e.g. `npm run ...
This command helps you create well-formatted commits following the Conventional Commits specification.
Basic usage:
/commit
With options:
/commit --no-verify
/commit --style=full
/commit --style=full --type=feat
--no-verify: Skip pre-commit checks (lint, build, etc.)--style=simple|full:
simple (default): Creates concise single-line commit messagesfull: Creates detailed commit messages with body and footer sections--type=<type>: Specify the commit type (overrides automatic detection)Pre-commit checks (unless --no-verify):
npm run lint, pnpm lint, or bun run lint) - ensure code qualitynpm run build) - verify build succeedsFile staging:
git statusgit addChange analysis:
git diff to understand changesCommit message creation:
<emoji> <type>[optional scope]: <description>
Example: ✨ feat(auth): add JWT token validation
<emoji> <type>[optional scope]: <description>
<body>
<footer>
Example:
✨ feat(auth): add JWT token validation
Implement JWT token validation middleware that:
- Validates token signature and expiration
- Extracts user claims from payload
- Adds user context to request object
- Handles refresh token rotation
This change improves security by ensuring all protected
routes validate authentication tokens properly.
BREAKING CHANGE: API now requires Bearer token for all authenticated endpoints
Closes: #123
| Type | Emoji | Description | When to Use |
|---|---|---|---|
feat | ✨ | New feature | Adding new functionality |
fix | 🐛 | Bug fix | Fixing an issue |
docs | 📝 | Documentation | Documentation only changes |
style | 🎨 | Code style | Formatting, missing semi-colons, etc |
refactor | ♻️ | Code refactoring | Neither fixes bug nor adds feature |
perf | ⚡️ | Performance | Performance improvements |
test | ✅ | Testing | Adding missing tests |
chore | 🔧 | Maintenance | Changes to build process or tools |
ci | 👷 | CI/CD | Changes to CI configuration |
build | 📦 | Build system | Changes affecting build system |
revert | ⏪ | Revert | Reverting previous commit |
The body should:
Good body example:
Previously, the application allowed unauthenticated access to
user profile endpoints, creating a security vulnerability.
This commit adds comprehensive authentication middleware that:
- Validates JWT tokens on all protected routes
- Implements proper token refresh logic
- Adds rate limiting to prevent brute force attacks
- Logs authentication failures for monitoring
The change follows OAuth 2.0 best practices and improves
overall application security posture.
Footer contains:
BREAKING CHANGE:Closes:, Fixes:, Refs:Co-authored-by: name <email>Reviewed-by:, Approved-by:Example footers:
BREAKING CHANGE: rename config.auth to config.authentication
Closes: #123, #124
Co-authored-by: Jane Doe <jane@example.com>
Scope should be:
Common scopes:
api, auth, ui, db, config, depsbutton, modal, headerparser, compiler, validatorAutomatically suggest splitting when detecting:
✨ feat: add user registration flow
🐛 fix: resolve memory leak in event handler
📝 docs: update API endpoints documentation
♻️ refactor: simplify authentication logic
⚡️ perf: optimize database query performance
🔧 chore: update build dependencies
✨ feat(auth): implement OAuth2 authentication flow
Add complete OAuth2 authentication system supporting multiple
providers (Google, GitHub, Microsoft). The implementation
follows RFC 6749 specification and includes:
- Authorization code flow with PKCE
- Refresh token rotation
- Scope-based permissions
- Session management with Redis
- Rate limiting per client
This provides users with secure single sign-on capabilities
while maintaining backwards compatibility with existing
JWT authentication.
BREAKING CHANGE: /api/auth endpoints now require client_id parameter
Closes: #456, #457
Refs: RFC-6749, RFC-7636
simple for quick, everyday commitsfull style for:
npx claudepluginhub webdevtodayjason/dev-kit --plugin dev-kit/commitStages unstaged changes based on git status and diff analysis, then creates a commit with a generated message. Uses current branch and recent commit history for context.
/commitStages changes and commits locally using Conventional Commits format. Analyzes git status/diffs, drafts typed message with scope, confirms with user before git add and commit.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitRuns pre-commit git checks, quality gates (lint, typecheck, tests), code review for issues; drafts conventional commit message; stages specific files and commits. Supports --no-verify, --amend, --push options.
/commitAnalyzes current git diff, generates 3 conventional commit message options (concise, detailed, comprehensive), presents for user selection, and executes git commit.