← ClaudeAtlas

git-commitlisted

Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
decebals/claude-code-java · ★ 599 · Code & Development · score 82
Install: claude install-skill decebals/claude-code-java
# Git Commit Message Skill Generate conventional, informative commit messages for Java projects. ## When to Use - After making code changes - User says "commit this" / "commit changes" / "create commit" - Before creating PRs ## Format Standard Use Conventional Commits format: ``` <type>(<scope>): <subject> <body> <footer> ``` ### Types (Java context) - **feat**: New feature (new API, new functionality) - **fix**: Bug fix - **refactor**: Code refactoring (no functional change) - **test**: Add/update tests - **docs**: Documentation only - **perf**: Performance improvement - **build**: Maven/Gradle changes - **chore**: Maintenance (dependency updates, etc) ### Scope Examples (Java specific) - Module name: `core`, `api`, `plugin-loader` - Component: `PluginManager`, `ExtensionFactory` - Area: `lifecycle`, `dependencies`, `security` ### Subject Rules - Imperative mood: "Add support" not "Added support" - No period at end - Max 50 chars - Lowercase after type ### Body (optional but recommended) - Explain WHAT and WHY, not HOW - Wrap at 72 chars - Reference issues: "Fixes #123" / "Relates to #456" ## Examples ### Simple fix ``` fix(plugin-loader): prevent NPE when plugin directory is missing Check for null before accessing plugin directory to avoid NullPointerException during initialization. Fixes #234 ``` ### Feature with breaking change ``` feat(api): add support for plugin dependencies versioning BREAKING CHANGE: PluginDescriptor now requires semantic versioning f