skills.rest
UnterrainerInformatik
UnterrainerInformatikOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit

Generate conventional commit messages for Java projects from staged changes.

Updated Apr 20, 2020
Search Tags:#git#code review#version control#conventional commits#github#java#commit message
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill git-commit-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill git-commit-unterrainerinformatik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent Git commit messages is often rushed or inconsistent across a team, making history hard to search and review. This Skill analyzes staged changes and produces properly formatted Conventional Commits messages tailored to Java projects. ## Core Features & Use Cases - Conventional Commits formatting: Generates messages with correct type, scope, subject, body, and footer following the Conventional Commits specification. - Java-specific guidance: Provides type and scope conventions for Java contexts such as modules, Maven/Gradle builds, and dependency updates. - Breaking change handling: Formats BREAKING CHANGE footers and migration notes when APIs change. - Use Case: After staging a bug fix in a plugin loader, ask for a commit and receive a message like "fix(plugin-loader): prevent NPE when plugin directory is missing" with a body referencing the fixed issue. ## Quick Start Stage your changes with git add, then ask the assistant to commit these changes with a conventional commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a conventional commit message?▼

Use the format type(scope): subject, followed by an optional body and footer. Choose a type like feat, fix, refactor, test, docs, perf, build, or chore, write the subject in imperative mood under 50 characters, and reference issues in the footer.

How to generate commit messages from staged git changes?▼

Stage your changes with git add, then let the Skill inspect git diff --staged to identify the scope and type of change. It produces a complete conventional commit message and can execute git commit with the generated message.

What commit types should I use for Java projects?▼

Use feat for new APIs or functionality, fix for bugs, refactor for restructuring without behavior change, test for test additions, docs for documentation, build for Maven or Gradle changes, perf for performance work, and chore for maintenance.

How do I mark a breaking change in a commit message?▼

Add an exclamation mark after the type or scope, such as feat(api)!, and include a BREAKING CHANGE footer explaining what changed and how to migrate. The Skill formats these automatically when API changes are detected.

When should changes be split into multiple commits?▼

Split commits when changes span unrelated concerns or mix types like a feature and an unrelated fix. Each commit should represent a single logical change with a clear, searchable subject line.

Related Skills

Explore More Software Engineering Skills→
gaia-iagaia-ia
4

Git Commit Helper

Generate conventional commit messages from staged Git diffs.

Official
Basic
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic