git-commit

Generate conventional Git commit messages for Java projects.

700|137|Updated Jan 30, 2026

Search Tags:#git #workflow #commit #java #generate #conventional

Ready to run

npx skills add https://github.com/decebals/claude-code-java --skill git-commit-decebals

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/decebals/claude-code-java/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/decebals/claude-code-java --skill git-commit-decebals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating clear, conventional Git commit messages for Java projects to communicate intent and changes effectively.

Core Features & Use Cases

Generate conventional commits following the standard format for Java projects.
Enforce type, scope, and subject rules to maintain consistency across PRs.
Provide examples and guidance to help users craft informative messages quickly.

Quick Start

After staging changes, instruct Claude Code to generate a commit message that describes the changes.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate conventional commit messages for Java projects?▼

To generate conventional commit messages for Java projects, stage your changes and instruct Claude Code to create a message describing the changes. The Skill outputs well-formed messages using the Conventional Commits format.

What is the conventional commits format for a git workflow?▼

The conventional commits format structures messages with a type (feat, fix, chore), an optional scope, a subject, and an optional body or footer. This enforces consistency across PRs to communicate intent and changes effectively.

Does this git commit generator support scopes and message bodies?▼

Yes, the git commit generator supports optional scopes and message bodies. It enforces type, scope, and subject rules to maintain consistency, and includes an optional body and footer for additional context.

When do I need to use different commit types like feat, fix, or chore?▼

You need different commit types like feat, fix, or chore when categorizing distinct changes in your git workflow. The Skill applies the correct type automatically based on whether changes represent features, bug fixes, or chores.

Can I use this to write commit messages for refactoring or performance improvements?▼

Yes, you can use this to write commit messages for refactoring or performance improvements. The Skill supports the refactor and perf types, alongside feat, fix, test, docs, and build, to accurately describe code changes.