Agent skill · software engineering · aiskillstore
commit-chat-push
Commit and push repository changes while also exporting and committing the Codex chat/session transcript that produced the feature. Use when the user asks Codex to commit, push, save provenance, include the chat, commit the session, attach the Codex conversation, or preserve the implementation chat from ~/.codex/sessions alongside code changes.
Why this skill is useful
Adds an executable script for exporting and committing Codex session transcripts alongside code changes, which is not standard practice.
What it needs
Requires python3 installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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. Run git status --short --branch. Run git remote -v and git branch --show-current when push behavior is not obvious. Review git diff and staged diff before committing. Never stage unrelated dirty files. If unrelated changes exist, leave them alone. 2. Verify the change. Run the narrowest meaningful tests or checks for the work. If tests are unavailable or fail for unrelated reasons, record that clearly in the final response. 3. Export the Codex transcript. Use an existing repo convention for transcripts if one exists, such as docs/codex-sessions/, codex-sessions/, .codex/chats/, or devlog/. Otherwise use docs/codex-sessions/. Before exporting, create a fresh marker with a tiny completed command: Copy the printed marker exactly, then run: If --require-anchor fails, wait briefly and rerun with the same marker. If it still fails, inspect candidate sessions manually and rerun with --session /path/to/rollout-....jsonl. 4. Review the exported transcript before staging. Read enough of the file to confirm it is the intended session. Search for obvious secrets or private material: 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. 5. Stage exactly the intended files. Include the exported transcript. Prefer explicit pathspecs over git add . when the worktree has unrelated changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit-chat-push