A coding workflow that checks a project's tests, code style, changed files, and full Git diff before creating a commit and optionally opening a pull request.

Use it when code is finished and you want to run tests and linting, inspect the changes, stage the right files, commit them, and optionally create a pull request.

It groups the final checks into one process, reducing the chance of committing broken, unfinished, insecure, or low-quality changes.

uvs-commit — Skill for Claude Code by utsavanand/uv-suite

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 utsavanand/uv-suite --skill uvs-commit

Clone the repo

git clone --depth 1 https://github.com/utsavanand/uv-suite

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-commit/github.svg)](https://agentmods.dev/skills/utsavanand/uv-suite/uvs-commit)

Your own site

<a href="https://agentmods.dev/skills/utsavanand/uv-suite/uvs-commit"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/utsavanand/uv-suite/uvs-commit"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 721 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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00721
Opus 5.5	$0.00016	$0.00288
Sonnet 5.5	$0.00008	$0.00144
Haiku 4.5	$0.00004	$0.00072

Measured 2mo ago against content hash 741498a265eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

uvs-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 2mo 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/uvs-commit/SKILL.md · 95 lines

How it starts

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

Intent

$ARGUMENTS

Current state

!git status --short 2>/dev/null | head -30 || echo "not a git repo"

!git diff --cached --stat 2>/dev/null || echo "nothing staged"

!git diff --stat 2>/dev/null || echo "no unstaged changes"

Pipeline — run these steps in order

1. Run tests

Find and run the project's test command. If tests fail, fix the failures before continuing. If they can't be fixed in 2 attempts, stop and report.

2. Run lint

If a lint command exists (npm run lint, ruff check, etc.), run it. Fix auto-fixable issues.

3. Quick slop check

Scan changed files for the most obvious patterns:

toBeTruthy() / toBeDefined() in test files
Bare except: pass in Python

Don't run the full /uvs-review --slop agent — just grep for mechanical patterns.

4. Review the diff

Read the full diff. Check for:

Correctness: does it do what it should?
Security: any obvious issues? (hardcoded secrets, missing auth checks)
Completeness: anything half-done or TODO'd?

If you find issues, fix them. If they need human input, stop and ask.

5. Stage and commit

Stage the relevant files (not .env, not node_modules, not build artifacts)
Write a commit message. If the user provided one in $ARGUMENTS, use it. Otherwise, write a concise message that describes the WHY, not the WHAT.
Commit.

6. Open PR (if requested)

If the user said "pr" in their arguments, or if on a feature branch:

Push the branch
Open a PR with gh pr create
Title: short, under 70 chars
Body: summary bullets + test plan

7. Checkpoint

After committing, write a checkpoint to latest.md in this session's checkpoint directory (shown below) with what was committed:

!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/checkpoint-helper.sh dir

Danger zones

!cat DANGER-ZONES.md 2>/dev/null || echo "No DANGER-ZONES.md"

Rules

If tests fail and can't be fixed quickly, STOP. Don't commit broken code.
If the diff touches a danger zone file, flag it before committing.
Prefer separate commits per logical change if there are unrelated changes staged.
Never commit .env, credentials, or secrets.

Read the full file on GitHub · 95 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.

2mo ago First seen · 95 lines · 39 tokens per session scan A 741498a265eb

Subscribe to this mod's changes

uvs-commit is a skill published in the GitHub repository utsavanand/uv-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 721 once invoked, about $0.0002 per session on Opus 5.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.

Code review Commits Git and workflow

uvs-commit