git-commit

Conventional Commits messages are generated by analyzing git status, git diff, and recent git log output to infer the change type and scope. The result follows the format type(scope): subject, with an optional body explaining why the change was made.

Stage files individually with git add followed by explicit paths, such as git add src/main/java/com/sample/llm/board/Board.java. This avoids accidentally including unrelated changes or sensitive files in the commit.

The common types are feat for new features, fix for bug fixes, docs for documentation, refactor for code restructuring, test for tests, chore for build and config changes, and style for formatting. Each type signals the intent of the change in the history.

Before committing, scan the changed file list for patterns like .env, credentials.json, secret.*, *.pem, and *.key. If detected, warn the user and confirm whether those files should be excluded from the commit.

HEREDOC preserves multi-line messages and special characters safely in shell commands. It prevents quoting errors when the commit body contains line breaks, Korean text, or punctuation.

These flags bypass safety checks or rewrite history, so they should only be used when the user explicitly requests them. Default commits should avoid both options to keep history and hooks intact.