java-git-commit

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.

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.

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.

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.

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.

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.