java-git-commit

Automate conventional commits for a Java project by enforcing Java-aware scopes and synchronizing DESIGN.md prior to committing. This workflow aligns commit patterns with JVM ecosystem conventions and ensures design documentation reflects code changes.

Yes, you can keep DESIGN.md synchronized during a git commit by triggering automatic design documentation updates before the commit process finalizes. This ensures architectural documentation stays current with the latest code modifications.

Yes, this conventional commit workflow works with Maven and Gradle projects. It applies Java-specific commit patterns to any project maintaining a DESIGN.md file and optionally integrates with CLAUDE.md when present.

The best way to enforce Java-specific scopes in conventional commits is to use a workflow that builds upon standard git-commit rules while applying JVM-aware scope definitions. This ensures team conventions align with the Java ecosystem.

No, you do not need a CLAUDE.md file to use this Java git commit workflow. A DESIGN.md file is required for synchronization, but the workflow only processes CLAUDE.md updates when that file is already present in the project.

You should synchronize design documentation before creating a git commit to ensure architectural decisions in DESIGN.md accurately reflect the code changes being committed. This prevents documentation drift and maintains project alignment.