Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
odysseus0 avatar

Commit

  • 520 installs
  • 82 repo stars
  • Updated March 12, 2026
  • odysseus0/symphony

Helps with git & pull requests tasks.

About

commit is a Claude Code skill for git & pull requests. It helps solo builders move faster with AI-assisted coding.

  • commit
  • Git & Pull Requests
  • AI-coding skill

Commit by the numbers

  • 520 all-time installs (skills.sh)
  • +2 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #105 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Jul 26, 2026 (Skillselion catalog sync)
npx skills add https://github.com/odysseus0/symphony --skill commit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs520
repo stars82
Last updatedMarch 12, 2026
Repositoryodysseus0/symphony

What it does

Helps with git & pull requests tasks.

Files

SKILL.mdMarkdownGitHub ↗

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): ..., 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 commit whose 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>

Related skills

Forks & variants (1)

Commit has 1 known copy in the catalog totaling 138 installs. They canonicalize to this original listing.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.