nette/plugins/nette-dev/skills/commit-messages
plugins/nette-dev/skills/commit-messages/SKILL.md
--- name: commit-messages description: Invoke BEFORE committing changes. Provides commit message conventions: lowercase, past tense, subject:description format. Use this skill whenever the user commits, creates commit messages, stages changes, uses /commit, tags releases, or discusses commit style - even for simple one-liner commits. --- ## Commit Message Style Follow these conventions for commit messages: ### Basic Rules - Subject line in lowercase, description (if present) uses normal sente
$ install --global
skillsauthnpx skillsauth add nette/claude-code plugins/nette-dev/skills/commit-messagesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 11:28 AM148.5s1 file scanned
SKILL.md
- name:
- commit-messages
- description:
- Invoke BEFORE committing changes. Provides commit message conventions: lowercase, past tense, subject:description format. Use this skill whenever the user commits, creates commit messages, stages changes, uses /commit, tags releases, or discusses commit style - even for simple one-liner commits.
Commit Message Style
Follow these conventions for commit messages:
Basic Rules
- Subject line in lowercase, description (if present) uses normal sentence case
- No period at the end of subject line
- Use past tense for verbs ("added", "fixed", not "add", "fix") - the commit describes what happened, so the git log reads as a chronological history
- Nouns are fine as-is ("fix" as noun is OK, e.g., "compatibility fix")
- Keep first line under 70 characters when possible
- Write in English only
Format
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.
Multi-line Messages
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.
Common Patterns
- Feature additions:
added [feature] - Bug fixes:
fixed [issue] - Releases:
Released version X.Y.Z(exception to the lowercase rule) - Deprecations:
[method] deprecated - Breaking changes: include "(BC break)" in message
- Work in progress:
wip
Routine/Maintenance Commits
Keep these simple, no additional context needed:
vendor- dependency updatescs- coding style fixestypos- typo corrections
Related Skills
nette/php-auto-fixer
tools
VerifiedTrustedCommunity
CRITICAL: Read BEFORE writing or modifying any PHP file. A PostToolUse hook automatically runs nette/coding-standard (ECS) on every PHP file after each Edit or Write. The fixer removes unused `use` statements - so never add `use` statements in a separate edit before the code that references them. Always include `use` imports in the same edit as the referencing code, or add the code first then `use` statements. This skill should be used whenever creating new PHP files, editing existing PHP code, adding methods, refactoring, or fixing bugs in PHP - even for small one-line changes.
40SKILL.mdUpdated Apr 28, 2026
nette/install-php-fixer
development
VerifiedTrustedCommunity
Install nette/coding-standard globally for PHP code style checking
40SKILL.mdUpdated Apr 28, 2026
nette/tracy-debugging
tools
VerifiedTrustedCommunity
Invoke when fetching web pages from localhost, debugging PHP errors, or interpreting Tracy output (BlueScreen, Tracy Bar, dump). Read BEFORE running curl or Chrome to any local development PHP URL – with Tracy >= 2.12 and a detected agent, Tracy mirrors BlueScreen, Tracy Bar and dumps as markdown into the JS console for easy machine reading. For Chrome MCP, call list_console_messages() to read Tracy output. Essential when: 500 error, blank page, PHP exception, slow page, N+1 queries, or inspecting variables with dump().
40SKILL.mdUpdated Apr 28, 2026
nette/nette-utils
tools
VerifiedTrustedCommunity
Provides Nette Utils helper classes. Use when working with Arrays, Strings, Image, Finder, FileSystem, Json, Validators, DateTime, Html element builder, Random, Callback, Type, or SmartObject from nette/utils. Do NOT use for Nette Schema, Nette Forms, Nette Database, Latte filters, or DI configuration.
40SKILL.mdUpdated Apr 28, 2026