Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages.

MITAuto-check: warningsDevelopment

Install Commit

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add OriginProtocol/origin-dollar --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OriginProtocol/origin-dollar commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/OriginProtocol/origin-dollar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit
GitHub stars
153
Token cost
~850 tokens
SKILL.md length
426 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages.

  • Works in 7 steps: Check git state → Inspect changes → Run targeted formatting → …
  • The user says commit it
  • SKILL.md covers Workflow and Safety rules
  • Calls git, yarn and npx

What it does

Commit is an agent skill from OriginProtocol/origin-dollar. Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages. Use when the user says commit it, commit this, commit changes, save my changes, or similar git commit requests.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: OUSD and OETH are stablecoins that passively accrue yield while you are holding it. The licence is MIT.

When your agent uses it

  • The user says commit it
  • Save my changes
  • Similar git commit requests

Example prompts

  • “/commit”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Check git state
  2. Inspect changes
  3. Run targeted formatting
  4. Stage files
  5. Generate commit message
  6. Commit
  7. Push only if requested

What it can do on your machine

Read from SKILL.md and the folder at commit ae82163. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • yarn
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, yarn and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit loads about 850 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 426 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~850

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • NoteMentions a .env fileSKILL.md:72
    - `.env` and `.env.*`
  • WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:117
    applied. Do not stop after staging and do not ask for confirmation if the user already requested a commit.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OriginProtocol/origin-dollar at commit ae82163, republished under its MIT licence (© OriginProtocol). 426 words, ~850 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages. Use when the user says commit it, commit this, commit changes, save my changes, or similar git commit requests.

Commit

Automate the full commit workflow: inspect changes, format only affected files, stage tracked and untracked files individually, generate a Conventional Commit message, and create the commit. The user asked for a commit because they want the commit created, not a plan.

Workflow

1. Check git state

Run git status.

Stop and tell the user if the repo is mid-merge, rebase, or cherry-pick. If there are no tracked or untracked changes, say Nothing to commit and stop.

2. Inspect changes

Run these in parallel:

  • git diff
  • git diff --cached
  • git status --porcelain
  • git log --oneline -5

Untracked files shown as ?? are often part of the current task and should normally be included.

3. Run targeted formatting

Collect candidate files with:

  • git diff --name-only
  • git diff --name-only --cached
  • git ls-files --others --exclude-standard

Only run formatters for changed files.

If any .sol files under contracts/tests/ changed:

bash
forge fmt <those-files>

If any .sol files not under contracts/tests/ changed:

bash
npx prettier --write --plugin=prettier-plugin-solidity <those-files>

If files under src/js/ or JS config files changed:

bash
yarn lint --fix
yarn prettier --write <changed-js-files>

Do not format the whole repository. If formatting fails and cannot be auto-fixed, report the issue and stop unless the user explicitly wants to proceed.

4. Stage files

Stage files individually. Do not use git add -A or git add ..

Include:

  • modified tracked files
  • new untracked files
  • files updated by formatters

Skip and warn on likely secrets:

  • .env and .env.*
  • names containing credential or secret
  • *.pem, *.p12, *.pfx
  • *.key private keys
Show full SKILL.md (194 more words)Show less
5. Generate commit message

Base the message on the staged diff from git diff --cached.

Format:

text
type(scope): description

Types:

  • feat
  • fix
  • refactor
  • perf
  • test
  • docs
  • chore

Suggested scopes in this repo:

  • lido
  • etherfi
  • ethena
  • origin
  • arm
  • deploy
  • js
  • cap
  • zapper
  • market
  • pendle
  • sonic
  • skill

If the change spans multiple unrelated areas, omit the scope. Use imperative mood, lowercase, no trailing period, and keep the subject under 72 characters.

6. Commit

Always run git commit unless an earlier safety stop applied. Do not stop after staging and do not ask for confirmation if the user already requested a commit.

Check the original user request for:

  • whether a co-author trailer was requested
  • whether a push was requested

Create the commit with git commit -m .... Afterward run git status to confirm success and report:

text
Committed <short-hash>: type(scope): description
7. Push only if requested

If the user explicitly asked to push, run git push or git push -u origin <branch> when needed. Otherwise do not push and do not ask.

Safety rules

  • Never amend unless the user explicitly asks
  • Never force push
  • Never use --no-verify
  • If hooks fail, fix the issue, re-stage, and create a new commit
  • If there is nothing to commit, stop

© OriginProtocol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/commit of OriginProtocol/origin-dollar.

Open the folder on GitHubat commit ae82163

Compare with similar skills

Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillOriginProtocol/origin-dollar153—~850Automated safety check: WarnMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from OriginProtocol/origin-dollar

  • Fork Test

    OriginProtocol/origin-dollar

    Generate Foundry fork tests for contracts that need real on-chain integration coverage.

    153 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Organize Test

    OriginProtocol/origin-dollar

    Reorganize Foundry test files (.t.sol) for readability and consistency without changing semantics.

    153 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Smoke Test

    OriginProtocol/origin-dollar

    Generate Foundry smoke tests that validate deployment health using DeployManager/Resolver against real on-chain state with pending governance applied.

    153 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Talos Action Development

    OriginProtocol/origin-dollar

    Develop, modify, review, and maintain standalone Talos actions in contracts/tasks/actions, including chain guardrails, contract bindings, transaction safety, schedules, action catalogues, and Talos…

    153 GitHub stars~896 tokensUpdated yesterday
    Auto-check passed
  • Unit Test

    OriginProtocol/origin-dollar

    Generate Foundry unit tests for a contract using this repository's conventions, structure, and naming.

    153 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Verify Deployment PR

    OriginProtocol/origin-dollar

    Verifies a POST-EXECUTION mainnet (or other network) smart-contract deployment PR for this repo: confirms every deployed contract is listed in the PR description, that the on-chain verified source…

    153 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Commit

What does Commit do?

Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages. Commit is an agent skill from OriginProtocol/origin-dollar. Handle git commits with auto-staging, targeted pre-commit formatting, and Conventional Commit messages.

When should I use Commit?

Commit fits situations like: the user says commit it; save my changes; similar git commit requests.

How do I install Commit in Claude Code?

Run `npx skills add OriginProtocol/origin-dollar --skill commit -a claude-code`. Or copy the skill folder (.codex/skills/commit in OriginProtocol/origin-dollar) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add OriginProtocol/origin-dollar --skill commit -a codex`. Or copy the skill folder (.codex/skills/commit in OriginProtocol/origin-dollar) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OriginProtocol/origin-dollar --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (git, yarn and npx). Our summary lists: Node.js.

Does Commit access the network?

SKILL.md contains no URLs. Its commands use git and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Commit use?

Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 850 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit?

Skills that share tags, products or a category with Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

OriginProtocol (a GitHub organization) maintains it in OriginProtocol/origin-dollar, which has 153 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

Source: OriginProtocol/origin-dollar on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.