commit

A Git commit command that stages selected or all changes, runs lint and TypeScript checks, and creates a commit. Git is the version-control system used to record code changes.

In plain words
What is it for?
Use it to make a normal commit, provide a custom message, stage specific files, amend the previous commit, or skip checks for a work-in-progress commit.
Why use it?
It catches common code-quality problems before changes are recorded and reduces repetitive commit preparation.

Command for Claude Code

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 commands/dork-labs/dorkos/commit
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.01169
Opus 5 $0.00006 $0.00584
Sonnet 5 $0.00002 $0.00234
Haiku 4.5 $0.00001 $0.00117

Measured yesterday against content hash cf73b6185c9e, 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 yesterday.

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.

.claude/commands/git/commit.md · 184 lines

How it starts

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

Git Commit

Stage and commit changes after validating that there are no lint or type errors.

Arguments

Parse $ARGUMENTS for these optional flags:

Argument Effect
-m "message" Use provided commit message instead of auto-generating
--amend Amend the previous commit instead of creating new one
--no-verify Skip lint and typecheck validation
<files...> Stage only specified files (default: all changes)

Examples:

  • /git:commit — Auto-generate message, stage all, validate
  • /git:commit -m "fix: resolve auth race condition" — Use provided message
  • /git:commit --amend — Amend previous commit
  • /git:commit src/lib/auth.ts — Only stage and commit specific file
  • /git:commit -m "wip" --no-verify — Quick WIP commit, skip checks

Task

Step 0: Parse Arguments

Extract flags from $ARGUMENTS:

  • Check for -m "..." or -m '...' — store as USER_MESSAGE
  • Check for --amend flag — store as AMEND=true
  • Check for --no-verify flag — store as SKIP_VERIFY=true
  • Remaining arguments are file paths — store as FILES

Step 1: Run Validation Checks (unless --no-verify)

Skip this step if --no-verify flag was provided.

Run lint and typecheck in parallel. Both must pass before proceeding.

pnpm lint
pnpm typecheck

If either fails: Stop and report the errors. Do not proceed to commit.

Step 2: Review Changes

Show the current state of the repository:

# Show status
git status

# Show staged changes
git diff --staged

# Show unstaged changes
git diff

Step 3: Stage Changes

Stage changes for commit:

If specific files were provided:

git add <files...>

Otherwise, stage all changes:

git add -A

If there are no changes to commit (or stage), report this and stop.

Read the full file on GitHub · 184 lines

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. yesterday First seen · 184 lines · 12 tokens per session scan A cf73b6185c9e

Subscribe to this mod's changes

commit is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,169 once invoked, about $0.0001 per session on Opus 5. 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.