Commit Goals - Produce a commit that reflects the actual code changes and the session context. - Follow common git conventions (type prefix, short subject, wrapped body). - Include both summary and rationale in the body. Inputs - Codex session history for intent and rationale. - , , and for actual changes. - Repo-specific commit conventions if documented. Steps 1. Read session history to identify scope, intent, and rationale. 2. Inspect the working tree and staged changes ( , , ). 3. Stage intended changes, including new files ( ) after confirming scope. 4. Sanity-check newly added files; if…