
Commit
- 138 installs
- 26.4k repo stars
- Updated July 24, 2026
- openai/symphony
This is a copy of commit by odysseus0 - installs and ranking accrue to the original listing.
Automates git commit creation with meaningful messages generated by AI for code changes.
About
The commit skill empowers agents to create well-structured git commits with AI-generated commit messages. It analyzes staged changes and produces descriptive, convention-following commit messages automatically. Perfect for developers who want consistent git history with minimal manual effort.
- Claude Code skill
- Agent capability extension
- Developer productivity
- Workflow automation
- Easy integration
Commit by the numbers
- 138 all-time installs (skills.sh)
- +5 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/openai/symphony --skill commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 138 |
|---|---|
| repo stars | ★ 26.4k |
| Last updated | July 24, 2026 |
| Repository | openai/symphony ↗ |
What it does
Automates git commit creation with meaningful messages generated by AI for code changes.
Who is it for?
Best when you want automated git workflows
Skip if: Non-git projects
What you get
- git commits with AI-generated messages
Files
Commit
Goals
- Produce a commit that reflects the actual code changes and the session
context.
- Follow common git conventions (type prefix, short subject, wrapped body).
- Include both summary and rationale in the body.
Inputs
- Codex session history for intent and rationale.
git status,git diff, andgit diff --stagedfor actual changes.- Repo-specific commit conventions if documented.
Steps
1. Read session history to identify scope, intent, and rationale. 2. Inspect the working tree and staged changes (git status, git diff, git diff --staged). 3. Stage intended changes, including new files (git add -A) after confirming scope. 4. Sanity-check newly added files; if anything looks random or likely ignored (build artifacts, logs, temp files), flag it to the user before committing. 5. If staging is incomplete or includes unrelated files, fix the index or ask for confirmation. 6. Choose a conventional type and optional scope that match the change (e.g., feat(scope): ..., fix(scope): ..., refactor(scope): ...). 7. Write a subject line in imperative mood, <= 72 characters, no trailing period. 8. Write a body that includes:
- Summary of key changes (what changed).
- Rationale and trade-offs (why it changed).
- Tests or validation run (or explicit note if not run).
9. Append a Co-authored-by trailer for Codex using Codex <codex@openai.com> unless the user explicitly requests a different identity. 10. Wrap body lines at 72 characters. 11. Create the commit message with a here-doc or temp file and use git commit -F <file> so newlines are literal (avoid -m with \n). 12. Commit only when the message matches the staged changes: if the staged diff includes unrelated files or the message describes work that isn't staged, fix the index or revise the message before committing.
Output
- A single commit created with
git commitwhose message reflects the session.
Template
Type and scope are examples only; adjust to fit the repo and changes.
<type>(<scope>): <short summary>
Summary:
- <what changed>
- <what changed>
Rationale:
- <why>
- <why>
Tests:
- <command or "not run (reason)">
Co-authored-by: Codex <codex@openai.com>