Stats
Actions
Tags
From director-mode-lite
Creates Conventional Commits with pre-commit checklists for scope, quality, tests, linting, formatting, and documentation. Ensures one logical change per commit before git commit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/director-mode-lite:smart-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a high-quality commit for current changes.
Create a high-quality commit for current changes.
<type>(<scope>): <description>
<body>
<footer>
| Type | Use When |
|---|---|
feat | New feature (user-visible) |
fix | Bug fix |
docs | Documentation only |
test | Adding/updating tests |
refactor | Code restructure (no behavior change) |
style | Formatting (no logic change) |
chore | Maintenance, dependencies |
perf | Performance improvement |
Module, component, or file affected:
feat(auth): add login endpointfix(api): handle null responsedocs(readme): update installation stepsfeat(user): add email verification
Implement email verification flow for new user registration.
Users must verify email before accessing protected features.
Closes #42
fix(api): handle null response in user endpoint
Previously threw uncaught exception when user not found.
Now returns 404 with proper error message.
Fixes #67
Before committing:
npx claudepluginhub claude-world/director-mode-liteGenerates concise conventional git commit messages prioritizing 'why' over 'what', with proper types, scopes, imperative mood, and atomic structure. Use when writing commits or learning best practices.
Guides Git commit messages to follow Conventional Commits v1.0.0 spec, covering types (feat, fix, refactor, etc.), scopes, structure, body, footers, and examples. Use for code commits and PR reviews.
Enforces git commit best practices with conventional commits format, atomic principles, type prefixes, and semantic versioning for clear, meaningful history. Use when committing code.