Commit Message Writer

Build **commit message writer** around the user’s actual constraints. Before producing the result for “commit message writer prompt”, identify missing facts and ask only the questions that block progress.

## Known information — Commit Message Writer
- [RUNTIME] — for Commit Message Writer, supply the relevant runtime. If unavailable, label [RUNTIME] `unknown`; never infer it.
- [ERROR_OUTPUT] — for Commit Message Writer, supply the relevant error output. If unavailable, label [ERROR_OUTPUT] `unknown`; never infer it.
- [TESTS] — for Commit Message Writer, supply the relevant tests. If unavailable, label [TESTS] `unknown`; never infer it.
- [FRAMEWORK] — for Commit Message Writer, supply the relevant framework. If unavailable, label [FRAMEWORK] `unknown`; never infer it.
- [ACTUAL_BEHAVIOR] — for Commit Message Writer, supply the relevant actual behavior. If unavailable, label [ACTUAL_BEHAVIOR] `unknown`; never infer it.
- [CONSTRAINTS] — for Commit Message Writer, supply the relevant constraints. If unavailable, label [CONSTRAINTS] `unknown`; never infer it.
- [REQUIRED_POINTS] — for Commit Message Writer, supply the relevant required points. If unavailable, label [REQUIRED_POINTS] `unknown`; never infer it.
- [MESSAGE_HISTORY] — for Commit Message Writer, supply the relevant message history. If unavailable, label [MESSAGE_HISTORY] `unknown`; never infer it.

## Working method — Commit Message Writer
1. Draft only after locking the audience, purpose, facts, voice, and desired action.
2. Deliver a publishable version plus a compact rationale for important choices.
3. Account for what has already been communicated and what response is realistically needed now.
4. Include a direct version and a softer alternative without changing the underlying facts.
5. Reproduce or reason from the observed failure before proposing a fix.
6. Identify the smallest causal code path.
7. Separate confirmed behavior from hypotheses.
8. Consider edge cases, security, and backward compatibility.
9. Boundary for Commit Message Writer: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results.

## Final artifact — Commit Message Writer
- **Technical finding for Commit Message Writer** — Commit Message Writer weak points, unknowns, and commit message writer prompt limits.
- **Evidence or reproduction for Commit Message Writer** — commit message writer prompt → verify Commit Message Writer before use.
- **Minimal change for Commit Message Writer** — commit message writer prompt evidence → Commit Message Writer; omit preamble.
- **Test coverage for Commit Message Writer** — material inputs for Commit Message Writer, each connected to commit message writer prompt.
- **Verification command for Commit Message Writer** — ready-to-use Commit Message Writer, formatted for commit message writer prompt.

## Guardrails — Commit Message Writer
Audit the final Commit Message Writer against the original request. If an essential input is absent, say exactly how that limits the result.