Commit Code With a Reviewed Codex Transcript
Implementation context is often lost after code is committed. This workflow guides transcript review, selective staging, commit creation, and branch publication.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "commit-chat-push" from https://skillstore.io/skills/bertona88-commit-chat-push.md and its manifest at https://skillstore.io/api/skills/bertona88-commit-chat-push/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "commit-chat-push". Commit this feature with the Codex transcript and push it.
Expected outcome:
Using "commit-chat-push". Include provenance, but do not expose command output.
Expected outcome:
Prepared the transcript with command output omitted, reviewed it for sensitive text, and included it with the selected changes.
Using "commit-chat-push". The branch has no upstream. Publish the reviewed commit.
Expected outcome:
Verified the configured remote, created the commit, established the branch upstream, and reported the push result.
Most static alerts are false positives caused by Markdown backticks, code fences, safe Git inspection commands, and defensive secret-search patterns. Confirmed risks include reading private Codex sessions, permitting raw-session commits, and pushing transcript content to a remote repository. The referenced redaction exporter is missing, so its privacy controls cannot be audited.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/bertona88-commit-chat-push/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/bertona88-commit-chat-push?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/bertona88-commit-chat-push?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bertona88-commit-chat-push/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/bertona88-commit-chat-push.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>bertona88. (2026). commit-chat-push security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bertona88-commit-chat-push/audits/6@techreport{bertona88-bertona88-commit-chat-push-2026,
author = {bertona88},
title = {commit-chat-push security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/bertona88-commit-chat-push/audits/6},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "commit-chat-push security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "bertona88"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/bertona88-commit-chat-push/audits/6"
identifiers:
- type: other
value: "skillstore:bertona88-commit-chat-push:audit:6"
description: "Skillstore immutable audit report identifier"
Commit a reviewed implementation transcript beside a completed feature for future maintenance.
Record selected development context for reviewers who need to understand how a change was produced.
Apply consistent checks before staging code, attaching a transcript, creating a commit, and pushing.
Use commit-chat-push to review my current changes, include a redacted Codex transcript, commit the intended files, and push the branch.
Review the diff, run the narrowest relevant tests, export the anchored session, scan it for secrets, then commit and push.
Find this repository's transcript convention, export the current anchored session there, exclude unrelated changes, show the staged diff, then commit and push.
Inspect the remote and upstream, verify the change, review the redacted transcript, stage explicit paths, summarize exposure risks, request confirmation, then push.
Author
bertona88License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
8c3e20bba512c392d9b02ee748b18e0b09d4982c
Maintenance freshness
7/24/2026
Usage
2 downloads · 73 views
File structure
Standardize Your Git Workflow
by Atman36
Inconsistent commits and branches make collaboration and releases harder to manage. This skill applies Conventional Commits, GitFlow, review practices, and pre-commit checks.
Manage Advanced Git Workflows
by wshobson
Complex Git history tasks can break branches, hide bugs, or slow reviews. This skill provides structured guidance for safe rebases, cherry-picks, bisects, worktrees, and recovery.
Manage Git Submodules Safely
by supercent-io
Git submodules can be hard to add, update, and remove without mistakes. This skill provides structured workflows for common submodule tasks.
Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Apply Diasporic Intelligence With Source Credit
by MinistaJazz
AI writing can erase sources or omit consent boundaries when discussing culturally rooted knowledge. This skill preserves attribution, provenance, revocation, and human authority.
Create Conventional Git Commits
by 21pounder
Manual commit preparation can miss staged changes, message style, or sensitive files. This skill reviews git state and helps create clear conventional commits.