commit-chat-push

Commit Chat Push

Overview

Use this skill to turn finished work into a commit that includes both the code changes and a redacted Markdown transcript of the Codex session that made them, then push the branch.

The helper script exports a transcript from local Codex JSONL sessions. Prefer the transcript over raw JSONL because raw sessions can contain system/developer instructions, encrypted reasoning blobs, full tool outputs, and secrets.

Workflow

1. Inspect repository state.
2. Run git status --short --branch.
3. Run git remote -v and git branch --show-current when push behavior is not obvious.
4. Review git diff and staged diff before committing.
5. Never stage unrelated dirty files. If unrelated changes exist, leave them alone.

1. Verify the change.
2. Run the narrowest meaningful tests or checks for the work.
3. If tests are unavailable or fail for unrelated reasons, record that clearly in the final response.

1. Export the Codex transcript.
2. Use an existing repo convention for transcripts if one exists, such as docs/codex-sessions/, codex-sessions/, .codex/chats/, or devlog/.
3. Otherwise use docs/codex-sessions/.
4. Run:

python3 "${CODEX_HOME:-$HOME/.codex}/skills/commit-chat-push/scripts/export_codex_session.py" \
  --repo "$(pwd)" \
  --output-dir docs/codex-sessions \
  --tool-output none

1. Review the exported transcript before staging.
2. Read enough of the file to confirm it is the intended session.
3. Search for obvious secrets or private material:

rg -n "sk-|ghp_|github_pat_|BEGIN .*PRIVATE KEY|Authorization|Bearer |password|secret|token|api[_-]?key" docs/codex-sessions

• If sensitive content appears, edit the transcript or rerun the exporter with stricter omission choices before committing.
• Do not commit raw ~/.codex/sessions/*.jsonl unless the user explicitly asks for raw logs after being warned about the risk.

1. Stage exactly the intended files.
2. Include the exported transcript.
3. Prefer explicit pathspecs over git add . when the worktree has unrelated changes.
4. Confirm with git diff --cached --stat and git diff --cached.

1. Commit.
2. Use the repo's commit-message style if visible.
3. Mention the transcript in the body when helpful, for example:

feat: add commit transcript workflow

Includes Codex session transcript: docs/codex-sessions/2026-05-03-commit-transcript.md

1. Push.
2. If the branch already has an upstream, run git push.
3. If it does not and a default remote exists, run git push -u origin HEAD.
4. If push is rejected, inspect the reason and use the repo's normal sync workflow. Do not force-push unless the user explicitly requests it.

Selecting A Session

By default, export_codex_session.py selects the newest Codex JSONL session whose session_meta.cwd matches the current repository. If that is wrong, rerun it with --session /path/to/rollout-....jsonl.

Useful options:

python3 "${CODEX_HOME:-$HOME/.codex}/skills/commit-chat-push/scripts/export_codex_session.py" --help

• --output-dir PATH: write a generated Markdown filename in PATH.
• --output PATH: write to an exact Markdown path.
• --session PATH: export a specific JSONL session.
• --tool-output none|brief|full: control command output included in the transcript. Default is none; use brief only after considering whether prior commands printed secrets or raw session JSON.
• --include-local-paths: include full local source paths in metadata. By default, home paths are shortened to ~.

Privacy Rules

• Treat the transcript as source-controlled provenance, not a private dump.
• Keep user and assistant messages, tool names, commands, and command exit status.
• Omit developer/system instructions, encrypted reasoning, token-count events, and bulky raw logs.
• Redaction is a helper, not a guarantee. Always scan the transcript before committing.