commit

A workflow for staging selected changes, committing them, creating a pull request, and merging that request into the main branch.

In plain words
What is it for?
Use it to create a branch, commit specific files, push the branch, open a pull request, merge it, and return to the main branch.
Why use it?
It gives a defined path from finished code to an integrated change while checking repository state and avoiding accidental staging of secrets.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/clearsmog/claude-skills/commit
Any agent
npx skills add clearsmog/claude-skills --skill commit
Clone the repo
git clone --depth 1 https://github.com/clearsmog/claude-skills

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 452 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00452
Opus 5 $0.00013 $0.00226
Sonnet 5 $0.00005 $0.00090
Haiku 4.5 $0.00003 $0.00045

Measured 2d ago against content hash 7d2ffeb220e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to commit — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commit/SKILL.md · 78 lines

What it actually says

Commit, PR, and Merge

Stage changes, commit with a descriptive message, create a PR, and merge to main.

Steps

  1. Check current state:
git status
git diff --stat
git log --oneline -5
  1. Create a branch from the current state:
git checkout -b <short-descriptive-branch-name>
  1. Stage files — add specific files (never use git add -A):
git add <file1> <file2> ...

Do NOT stage .claude/settings.local.json or any files containing secrets.

  1. Commit with a descriptive message:

If $ARGUMENTS is provided, use it as the commit message. Otherwise, analyze the staged changes and write a message that explains why, not just what.

git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"
  1. Push and create PR:
git push -u origin <branch-name>
gh pr create --title "<short title>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>

## Test plan
<checklist>
EOF
)"
  1. Merge and clean up:
gh pr merge <pr-number> --merge --delete-branch
git checkout main
git pull
  1. Report the PR URL and what was merged.

Important

  • Always create a NEW branch — never commit directly to main
  • Exclude settings.local.json and sensitive files from staging
  • Use --merge (not --squash or --rebase) unless asked otherwise
  • If the commit message from $ARGUMENTS is provided, use it exactly
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 78 lines · 25 tokens per session scan A 7d2ffeb220e7

Subscribe to this mod's changes

commit is a skill published in the GitHub repository clearsmog/claude-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 452 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to commit, differing in 3 lines, and is treated as a copy.

Related

Other skills, from other repositories

ac-commit-manager

Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.

majiayu000/claude-skill-registry · 31 tokens

om-auto-continue-pr-loop

Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and checkpoint discipline (integration tests + screenshots for UI), runs the full gate at completion, keeps spec-only design PRs…

open-mercato/skills · 110 tokens

om-open-pr

Shared PR opener for the auto pipeline — commits the worktree, pushes, reuses an existing PR or opens a ready (non-draft) PR against the configured base branch with the unified body template, applies the full SDLC label set with rationale comments, and for issue-driven runs hands the issue back and releases the lock.…

open-mercato/skills · 83 tokens

om-auto-create-pr-loop

Advanced om-auto-create-pr for long, multi-step spec implementations needing resumability and strict step tracking — run folder (PLAN/HANDOFF/NOTIFY), one lean commit per Step, checkpoint verification every 5 Steps with integration tests and UI screenshots, full gate at completion, ready labeled PR. Resumable via…

open-mercato/skills · 86 tokens

github-awesome-copilot-git-commit

Generate high-quality, atomic Conventional Commits by analyzing Git changes, recommending logical commit boundaries, validating commit messages, and assisting with PRs, changelogs, and releases.

tuanductran/hr-skills · 45 tokens

om-check-and-commit

Verify that the current branch is ready to publish by running every configured validation command in order, fix straightforward failures (including locale-file drift when the repo checks it), and once everything passes commit and push the current branch. Use when the user asks to check the branch, make CI-style…

open-mercato/skills · 70 tokens