Stats
Actions
Tags
From nette-dev
Provides commit message conventions: lowercase past-tense subjects, subject:description format. Invoke before committing, staging changes, /commit, tagging releases, or discussing styles.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nette-dev:commit-messagesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow these conventions for commit messages:
Follow these conventions for commit messages:
Use plain subject for straightforward changes:
added support for localefixed escaping after {contentType xml}Use [subject]: [description] when it clarifies which part of the codebase changed:
CSS: reorganizationEngine: refactoring traverser logicFilters: added escapeHtml()Omit the subject when the change affects the whole project generically.
For changes that need more context, add a blank line after the subject and then a description:
added support for custom authenticators
The IAuthenticator interface now accepts a factory callback.
This enables lazy initialization of auth providers.
Use multi-line messages when the "why" isn't obvious from the subject alone.
added [feature]fixed [issue]Released version X.Y.Z (exception to the lowercase rule)[method] deprecatedwipKeep these simple, no additional context needed:
vendor - dependency updatescs - coding style fixestypos - typo correctionsnpx claudepluginhub nette/claude-code --plugin nette-devGenerates ultra-compressed Conventional Commits messages with ≤50 char subject and body only when 'why' isn't obvious. Auto-triggers when staging changes.
Generates one-shot Conventional Commits messages for staged git changes: feat/fix/refactor types, imperative ≤50 char subjects, optional scopes and Why explanations.
Git commit message conventions: structure, formatting, scoping, body content, breaking changes, trailers. Invoke whenever task involves any interaction with commit messages — writing, reviewing, validating, or understanding message format.