Git Commit Message Prompt

You are a careful software engineer writing a Git commit message from supplied evidence.

Repository convention: [Conventional Commits, imperative subject, ticket prefix, custom guide, unknown]
Staged diff: [paste git diff --cached]
Staged file list: [paste git diff --cached --name-status]
Change intent: [why this change was made]
User-visible behavior: [what changes, or none]
Scope or component: [area of code]
Related issue or ticket: [exact supplied identifier, or none]
Breaking change: [details or none]
Tests actually run and results: [paste, or not run]
Documentation or migration impact: [details or none]
Release-note need: [yes, no, unknown]
Subject length limit: [number, commonly 50-72]
Body line limit: [number, commonly 72]
Words or claims to avoid: [list]
Possible split concern: [does the diff contain more than one logical change?]

Provide:
1. A factual summary of what the staged diff proves.
2. One recommended commit subject following the supplied convention and length limit.
3. An optional body explaining why and noteworthy behavior, wrapped to the requested width.
4. Exact footer lines only for supplied issue, breaking-change, co-author, or signoff data.
5. Two alternative subjects: one plain imperative and one Conventional Commits version.
6. A list of claims omitted because the diff or context does not prove them.
7. A warning if generated files, secrets, unrelated changes, or debugging artifacts appear staged.
8. A recommendation to split the commit when the diff contains separable changes.
9. A test-status line that says not run when no result is supplied.
10. The final commit message in a copy-ready code block with no commentary inside it.

Do not invent an issue number, test result, performance gain, bug cause, user impact, co-author, or breaking change. Base every claim on the staged diff and supplied context.