git-commit

Generate conventional commit messages for staged Java code changes.

23|7|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/hzy970907/fish-claude-code --skill git-commit-hzy970907
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/hzy970907/fish-claude-code/tree/main/skills/git-commit
Command: npx skills add https://github.com/hzy970907/fish-claude-code --skill git-commit-hzy970907

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized, informative Git commit messages, ensuring consistency and clarity in your project's commit history.

Core Features & Use Cases

  • Conventional Commits: Adheres to the Conventional Commits specification for structured commit messages.
  • Java Context: Tailored with Java-specific types and scopes for relevant project contributions.
  • Use Case: After refactoring a module, use this Skill to generate a refactor commit message that clearly explains the changes and their purpose.

Quick Start

Use the git-commit skill to create a commit message for the staged 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 staged Java code changes?

To generate conventional commit messages for staged Java code changes, use this Skill to analyze your staged files and output structured commit types like feat, fix, or refactor with Java-specific scopes. It enforces imperative mood and subject line length limits automatically.

What is the conventional commits format and how does it apply to Java projects?

The conventional commits format structures commit messages with types, scopes, and descriptions. For Java projects, this Skill applies Java-specific scopes and supports types like feat, fix, refactor, test, docs, perf, build, and chore to ensure consistent version control history.

Can I include breaking changes and issue tracking in my automated git commit messages?

Yes, you can include breaking changes and issue tracking in your automated git commit messages. This Skill supports optional body and footer sections specifically designed for documenting breaking changes and linking issue tracking references within the conventional commits structure.

Does this conventional commit generator work with Java-specific scopes and project structures?

Yes, this conventional commit generator works with Java-specific scopes and project structures. It is tailored for Java development contexts, ensuring that commit types and scopes align with standard Java project contributions and refactoring scenarios.

What's the best way to automate git commit messages for version control consistency?

The best way to automate git commit messages for version control consistency is to use this Skill on your staged code changes. It standardizes your commit history by enforcing the conventional commits specification, imperative mood, and length constraints without manual formatting effort.

Why does my conventional commit message need to use imperative mood and subject line limits?

Your conventional commit message needs imperative mood and subject line limits to adhere to the conventional commits specification. This Skill automatically enforces these constraints on your Java commit messages to maintain a clean, readable, and standardized project commit history.