java-git-commit

Name: java-git-commit
Availability: InStock
Author: mdproctor

Automate Java commit workflows with mandatory DESIGN.md synchronization.

1|5|Updated Mar 29, 2026

Search Tags:#git #commit #java #code-review #conventional-commits #design-md

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Java Git Commit Helper extends the core git-commit workflow to inject Java/Quarkus-specific context and guarantees DESIGN.md synchronization via the java-update-design skill, so architecture considerations are always kept up to date in your commits.

Core Features & Use Cases

Extend git-commit with Java/Quarkus-specific subject scope suggestions and build awareness.
Always sync DESIGN.md before committing to keep architectural documentation in sync with code changes.
Integrate with update-claude-md to propose CLAUDE.md updates when present.
Requires explicit user confirmation before performing the final commit in Java repositories.

Quick Start

In a Java/Maven/Gradle repository, say commit to activate the Java Git Commit workflow with automatic DESIGN.md synchronization.

Frequently Asked Questions about java-git-commit

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

FAQPage Schema

How do I automate Java git commits with design documentation synchronization?▼

Automating Java git commits with design documentation synchronization requires a workflow that updates DESIGN.md files before committing, applies Java-specific scope guidance, and requests explicit user confirmation before finalizing the commit in Maven or Gradle repositories.

What is conventional commit scope guidance for Java and Quarkus repositories?▼

Conventional commit scope guidance for Java and Quarkus repositories provides build-aware subject line suggestions tailored to the project structure, ensuring commits align with architectural changes and maintain consistent hygiene across Maven and Gradle builds.

Does the Java commit workflow require a DESIGN.md file to be present?▼

Yes, the Java commit workflow mandates DESIGN.md presence to enforce architectural documentation synchronization. It integrates with the java-update-design process to keep design documents in sync with code changes before any commit is authorized.

How do I update CLAUDE.md when committing Java code changes?▼

To update CLAUDE.md when committing Java code changes, the workflow integrates with the update-claude-md process to propose updates automatically when the file is present, ensuring project context stays aligned with recent architectural modifications.

Can I use this automated commit workflow with Gradle projects?▼

Yes, you can use this automated commit workflow with Gradle projects. It supports both Maven and Gradle repositories, applying Java-specific context, enforcing DESIGN.md synchronization, and requiring explicit confirmation before executing the final commit.

Why does my Java commit workflow require explicit user confirmation before committing?▼

Your Java commit workflow requires explicit user confirmation before committing to prevent unintended changes from entering the repository. This safeguard ensures you review the synchronized DESIGN.md updates and proposed CLAUDE.md modifications before finalizing the commit.