generate-commit-messagelisted

# Generate Commit Message Produce evidence-based commit messages that follow Conventional Commits 1.0.0. Treat every message as a recommendation: inspect changes without modifying the repository, and never run `git add`, `git commit`, or another command that changes Git state. ## Gather the Change Evidence 1. Read applicable repository instructions and explicit commit policies. 2. Use a user-provided diff, patch, file list, or change summary when that is the requested source. 3. Otherwise, verify that the current directory is in a Git worktree and inspect all uncommitted changes: - Run `git status --short`. - Read both `git diff --cached` and `git diff`, including their `--stat` summaries when the patch is large. - List untracked paths with `git ls-files --others --exclude-standard`, then inspect relevant text files. Skip binary, generated, vendored, secret-bearing, or excessively large files and disclose any skipped context that could affect the result. 4. Inspect recent commit subjects only when useful for established scope names or trailer style. Do not copy malformed history or change the default message language from English unless an explicit repository policy or the user requires it. 5. If there are no changes and no usable user-provided description, state that there is not enough change evidence to generate a commit message. Base the message on the observed behavior and intent of the whole change. Do not infer issue numbers, breaking behavior, migration r