# Commit Code with a Codex Transcript

Teams often lose the reasoning behind a code change. This skill exports a redacted Codex transcript, commits it with the change, and pushes the branch.

## Install

```bash
npx skillstore add bertona88/commit-chat-push
```

## Metadata

- - Slug: bertona88-commit-chat-push
- - Version: 1.0.0
- - Author: bertona88
- - GitHub username: bertona88
- - License: MIT
- - Repository: https://github.com/bertona88/commit-chat-push/tree/main/
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: scripts, network, filesystem, env\_access, external\_commands
- - Quality score: 72
- - Public page: https://skillstore.pages.dev/skills/bertona88-commit-chat-push
- - Manifest: https://skillstore.pages.dev/api/skills/bertona88-commit-chat-push/manifest

## Capabilities

- Guides review of git status, diffs, staged files, and branch state.
- Exports Codex JSONL sessions into Markdown transcripts.
- Redacts common secret patterns and shortens home-directory paths.
- Includes tool calls, commands, command status, and visible chat messages.
- Stages the transcript with selected code changes for one commit.
- Pushes the current branch using normal git upstream behavior.

## Use Cases

- Preserve Feature Provenance: Commit the code change and a readable transcript that explains how the change was produced.
- Review AI-Assisted Work: Attach a concise Codex session record so reviewers can inspect prompts, actions, and verification steps.
- Document Delivery Evidence: Keep a source-controlled record of implementation context for audits, handoffs, and release notes.

## Prompt Templates

### Commit Current Work

```
Use commit-chat-push to review my changes, export the Codex transcript, commit both, and push the branch.
```

### Commit With Careful Staging

```
Use commit-chat-push, but stage only the files related to this task and the exported transcript.
```

### Export A Specific Session

```
Use commit-chat-push with a specific Codex session path, then commit the transcript with these changes.
```

### Audit Before Push

```
Use commit-chat-push, scan the transcript for secrets, show the staged summary, then push only after the review passes.
```

## Limitations

- Redaction is pattern-based and cannot guarantee removal of every secret.
- The workflow requires access to local Codex session files.
- Command output is omitted by default and must be enabled deliberately.
- It does not resolve merge conflicts or failed push policies automatically.

## Best Practices

- Review the generated transcript before staging it.
- Keep command output disabled unless it is needed for audit context.
- Use explicit git pathspecs when unrelated files are dirty.

## Anti Patterns

- Do not commit raw Codex JSONL session files by default.
- Do not use full tool output when commands may have printed secrets.
- Do not force-push unless the user explicitly requests it.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T14:46:01.105\+00:00
- - Summary: Static analysis found many command, filesystem, and sensitive-data patterns. Most high-volume hits are Markdown transcript records, but the skill intentionally reads Codex session files and can commit a transcript to a remote repository. No prompt injection or confirmed malicious intent was found, but publication should carry a privacy warning.

## Stats

- - Views: 73
- - Downloads: 1
- - Favorites: 0
- - Popularity score: 0