iso-commit

iso-commit is a skill for Claude Code, Codex from IsaiaScope/ai. It costs 0 tokens per session (2,380 once invoked), scanned A, original, MIT.

A Git helper for turning current code changes into commits with clear Conventional Commits messages, such as `fix(auth): handle expired sessions`. Git is a tool for tracking changes to code.

In plain words
What is it for?
Use it to check whether a commit is possible, review recent commit style, stage changes, and create one or several commits when explicitly requested.
Why use it?
It creates consistent, readable commit history while letting you choose whether to commit all changes, only staged changes, or separate groups of changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to check whether a commit is possible, review recent commit style, stage changes, and create one or several commits when explicitly requested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/isaiascope/ai/iso-commit
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.

Any agent
npx skills add IsaiaScope/ai --skill iso-commit
Clone the repo
git clone --depth 1 https://github.com/IsaiaScope/ai

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for iso-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/isaiascope/ai/iso-commit/github.svg)](https://agentmods.dev/skills/isaiascope/ai/iso-commit)
Your own site
<a href="https://agentmods.dev/skills/isaiascope/ai/iso-commit"><img src="https://agentmods.dev/badge/skills/isaiascope/ai/iso-commit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for iso-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/isaiascope/ai/iso-commit"><img src="https://agentmods.dev/badge/skills/isaiascope/ai/iso-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,380 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00000 $0.02380
Opus 5.5 $0.00000 $0.00952
Sonnet 5.5 $0.00000 $0.00476
Haiku 4.5 $0.00000 $0.00238

Measured 6d ago against content hash 9b26a08f1a93, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

iso-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 6d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/commit.sh, scripts/commit.test.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/iso-commit/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

iso-commit

Turn the current changes into one commit with a message a human will still understand in six months.

Invocation: /iso-commit [--staged] [--split].

flag effect
(none) git add -A — staged, unstaged, and untracked — then one commit
--staged commit the index only; stage nothing
--split group the diff by concern and make several commits instead of one

Commit everything, and ask before leaving anything out. The default stages every staged, unstaged and untracked path and commits it without asking. Never drop a path from the commit on your own judgement: "looks like another session's work", "unrelated", "still being edited" are all questions for the user, not decisions for you. If something looks like it should stay out, stop before committing, list those paths, and ask. The user decides what gets committed, not the agent.

Never commit unless the user asked. /iso-commit typed by the user is the only trigger. Do not commit at the end of iso-write, after making edits, or because a task "feels done" — the rest of the iso-* chain deliberately leaves the tree uncommitted, and this skill does not change that.

Flow

Mechanics live in skills/iso-commit/scripts/commit.sh. Run it by absolute path.

  1. Preflight — commit.sh preflight [--staged]. Non-zero: print its message and stop. Checks repo, branch (rejects detached HEAD), and that there's something to commit.
  2. Read the change — git diff HEAD (or git diff --cached with --staged), plus git log --oneline -10 to match the repo's existing subject style. Also read the repo's commitlint rules — commitlint.config.*, .commitlintrc*, or the commitlint key in the root package.json. They outrank this file: a scope-empty: never rule makes the scope required, a scope-enum limits it to the listed names, and length or case rules override the defaults below.
  3. Stage — commit.sh stage [--staged]. Runs the credential guard first and exits 2 without touching the index if it trips. On exit 2, print the blocked paths and stop; do not work around it.
  4. Write the message to a temp file, following the format below. Then commit.sh lint <msgfile>: it runs the repo's own commitlint on the message and names the broken rule. Fix and lint again until it prints lint=ok (or lint=skipped when the repo has no commitlint). Linting here means the commit-msg hook never becomes the first place a rule shows up.
  5. Branch gate — commit.sh gate "<subject>", then commit.sh land <action> <branch>. See below.
  6. Commit — commit.sh commit <msgfile>. Hooks run on purpose (commitlint gates the subject, version-bump reads it). If a hook rejects the commit, fix the message and retry — never --no-verify. If it reports paths that were staged but not committed (exit 4: the commit exists, a pre-commit hook dropped them), stage those paths and amend with git commit --amend --no-edit. Nothing staged is ever left behind.
  7. Report — print the message and the short SHA the script echoed. Add one line: wrong? git commit --amend.

Read the full file on GitHub · 162 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 6d ago Changed · +5 lines 9b26a08f1a93
  2. 1mo ago First seen · 157 lines · 0 tokens per session scan A daa08fdbe73d

Subscribe to this mod's changes

iso-commit is a skill published in the GitHub repository IsaiaScope/ai (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,380 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

spec-apply

Implement an OpenSpec change's tasks in parallel - read the task queue, plan file-disjoint waves, dispatch one agent per task into its own worktree, verify, tick the checkbox, commit, repeat. Use when the user says "apply the change", "implement the change", "run the tasks", "work the tasks in parallel", "fan out the…

pivoshenko/pivoshenko.ai · 188 tokens

spec-propose

Draft the OpenSpec change artifacts - proposal.md, the specs/ delta, design.md, tasks.md - on a fresh branch, install the wave rules that make tasks.md parallel-safe, validate, and commit. Use when the user says "propose this", "write the proposal", "spec this out", "/spec-propose", "turn this into an OpenSpec…

pivoshenko/pivoshenko.ai · 229 tokens

git-commit

Run git commit using Angular conventional commit format (header + footer only, no body). Use when the user asks to commit, create a commit, /git-commit, or save changes to git. Also trigger on "snapshot this", "save my work", "check in changes", "wrap up", "ship this locally", or whenever the user finishes a logical…

pivoshenko/pivoshenko.ai · 149 tokens

spec-archive

Fold a completed OpenSpec change into the project's specs, commit the move, and open the PR - the last link in the spec chain. Wraps /opsx:archive, which is git-blind. Use when the user says "archive the change", "archive that spec", "/spec-archive", "fold this into the specs", "close out the change", "it's done, land…

pivoshenko/pivoshenko.ai · 207 tokens

git-issue-start

Take a GitHub issue from open to a checked-out branch - assign it to you, mark it in progress if the repo has such a label, derive a conventional branch name from its type: label, branch off the detected base. Use for "start issue 42", "work on #42", "/git-issue-start 42", "let's do 42", "pick up that issue", "take…

pivoshenko/pivoshenko.ai · 174 tokens

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

guanyang/open-agent-hub · 22 tokens