commit Skill
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work. Published by openai in symphony.
Decision snapshot
Is this a fit?
Developers using symphony, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
27 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is commit Skill?
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work. Published by openai in symphony. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using symphony
Declared skill metadata
- Source file: .codex/skills/commit/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use commit Skill
- Use it for developers using symphony.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/symphony
- Skill file: .codex/skills/commit/SKILL.md
What it does
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
Skill instructions
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, and git diff --staged for 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): ..
Verified compatibility and discovery
Frequently asked questions
What is commit?
commit is a open-source AI agent skill with Copy skill directory. Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
Who is commit best for?
commit is best for reusing agent instructions, scripts, and references.
How do I install commit?
Install or run commit using Copy skill directory. Check commit for the latest setup command.
Is commit actively maintained?
commit may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
