dump-commit

A quick Git commit workflow that stages all files, checks for likely secrets, and creates a short commit message.

In plain words
What is it for?
Use it for a fast save of the current changes, optionally supplying the commit message.
Why use it?
It saves time when you need to record the current work without reviewing a detailed diff.

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/thaitype/chief/dump-commit
Any agent
npx skills add thaitype/chief --skill dump-commit
Clone the repo
git clone --depth 1 https://github.com/thaitype/chief

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 411 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.00050 $0.00411
Opus 5 $0.00025 $0.00205
Sonnet 5 $0.00010 $0.00082
Haiku 4.5 $0.00005 $0.00041

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

Security

Grade A, and why

dump-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.

skills/misc/dump-commit/SKILL.md · 53 lines

What it actually says

Commit all current changes with minimal token usage.

Arguments

Optional: a commit message string. If provided, use it as-is. If not provided, auto-generate from file names.

Steps

1. Check for secrets

Run git status. If any staged or untracked file matches these patterns, warn the user and STOP — do not commit:

  • .env*
  • *credentials*
  • *secret*
  • *.pem
  • *.key

2. Stage all files

git add -A

3. Generate or use commit message

If the user provided a message in the arguments → use it directly.

If no message was provided, generate a 1-line message using these sources (in priority order):

  1. Recent conversation context — if the conversation contains clear context about what was just done (e.g. "add chief-retro skill", "fix upgrade script"), use that to write a meaningful message.
  2. File names from git diff --cached --stat — if no conversation context, fall back to summarizing changed file names (e.g. wip: update chief-agent, chief-plan, upgrade.sh).

Do NOT read file content or full diffs. Keep the message under 72 characters.

4. Commit

git commit -m "<message>"

Rules

  • NEVER read file content or full diffs — only --stat output
  • NEVER ask the user to review the message — just commit
  • NEVER add Co-Authored-By or multi-line messages
  • If nothing to commit (clean working tree), say so and stop
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 · 53 lines · 50 tokens per session scan A d33be6cecbe4

Subscribe to this mod's changes

dump-commit is a skill published in the GitHub repository thaitype/chief (56 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 411 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens