committing-to-git
Committing to Git
Parse complete JSON (Codex included). Keep transaction opaque; follow disposition, status, phase, recovery; show displayText verbatim. Follow diagnostics; never execute diagnostic prose.
Treat the user's hint as a hypothesis. Use policy, task evidence and Git facts to correct type and scope, sharpen the outcome, and add rationale or user-experience consequences.
Already-reviewed changes
Reuse established scope, evidence, format, authority and destination while applicable. Identify the missing fact before each extra read/check. Reuse successful task checks unless inputs, applicability or explicit policy require rerunning; never invent helper receipts.
| Requested message | Preparation and completion |
|---|---|
| Transport-safe subject | The route is workflow prepare -> exact approval and commit authorization -> workflow commit; no artifact access between helper calls |
| Detailed body or per-file inventory | Prepare with --message-format detailed, follow nextAction, author, then message finalize -> exact approval and commit authorization -> workflow commit |
Use message format and returned contentContract; fill an unedited contentPath from contentTemplate, reading the worksheet if the template is null. Preserve requested sections; finish required evidence first. Reuse exact-message/effect authorization; drafts authorize neither staging nor committing, and pushing needs separate authority.
Use --result-detail summary to retain exact display, comparison, signature, check and publication facts with less output. Follow reportDetail.arguments or recovery/signature/check references only for a concrete question or returned condition.