Stage all tracked and untracked repository changes and create a git commit with a concise, high-signal message. Use when the user wants Codex to commit current work, prepare a clean checkpoint, or write a commit message from the staged or unstaged diff. Always enforce a commit subject of 88 characters or fewer and add a body only when the change is complex enough to need extra context.
Stage every current change and create one non-interactive commit.
git status --short and review the diff when the scope is unclear.git add -A unless the user explicitly asks for partial staging.git commit -m "<subject>" for subject-only commits.
Use multiple -m flags when adding a body.Keep the subject specific and compact.
Good subjects:
Fix invoice export sorting for multi-period reportsAdd retry handling for failed S3 metadata writesRefactor model summary parsing for quarterly filingsAvoid subjects that are vague or mechanical:
updatesfix stuffchange filesaddress review commentsUse a body only when it adds context that would help a reviewer later. Keep the body short and factual. Focus on why the change exists, notable tradeoffs, or any important side effects.
Example with body:
Refactor company sync to batch Dynamo writes
Reduce write amplification during large syncs by grouping updates per company.
This keeps the handler under the timeout threshold and preserves existing retry behavior.
Do not create an empty commit unless the user explicitly asks for one. If there are no changes, say so instead of committing. If unrelated user changes are present, commit them together only because this skill is specifically for staging all changes. If the repo blocks the commit with hooks or validation, surface the failure clearly.