code-notify: Command for Claude Code

.claude/commands/commit.md

commit is a command for Claude Code from mylee04/code-notify. It costs 6 tokens per session (358 once invoked), scanned A, original, MIT.

A command that checks code changes and creates a formatted Git commit, which is a saved checkpoint in a project's version history.

In plain words
What is it for?
Use it after a feature or fix is ready to run tests, inspect the changes, choose a conventional message type, and create the commit.
Why use it?
It reduces the chance of committing failing tests, lint problems, sensitive environment files, or unclear commit messages.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is mylee04/code-notify's own configuration. It tells Claude Code how to work on code-notify itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything code-notify configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mylee04/code-notify. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mylee04/code-notify/main/.claude/commands/commit.md
Clone the repo
git clone --depth 1 https://github.com/mylee04/code-notify

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.

agentmods badge for commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/mylee04/code-notify/commit/github.svg)](https://agentmods.dev/commands/mylee04/code-notify/commit)
Your own site
<a href="https://agentmods.dev/commands/mylee04/code-notify/commit"><img src="https://agentmods.dev/badge/commands/mylee04/code-notify/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 commit

Your own site · 80×15
<a href="https://agentmods.dev/commands/mylee04/code-notify/commit"><img src="https://agentmods.dev/badge/commands/mylee04/code-notify/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 358 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.00006 $0.00358
Opus 5.5 $0.00002 $0.00143
Sonnet 5.5 $0.00001 $0.00072
Haiku 4.5 $0.00001 $0.00036

Measured 1mo ago against content hash 94c4563e3bb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

.claude/commands/commit.md · 82 lines

What it actually says

Commit Changes

What This Command Does

  1. Checks for uncommitted changes
  2. Runs tests to verify code works
  3. Generates appropriate commit message
  4. Creates the commit

When to Use

  • After completing a feature or fix
  • When changes are ready to be saved

Process

1. Pre-Commit Checks

# Run tests
make test

# Check for lint issues
shellcheck bin/code-notify lib/code-notify/**/*.sh

2. Review Changes

git status
git diff --stat

3. Commit Message Format

type: brief description

- Detail 1
- Detail 2
Types
Type Use For
feat New feature
fix Bug fix
docs Documentation
refactor Code refactoring
test Adding tests
chore Maintenance

4. Example Messages

feat: add WSL support for notifications

- Detect WSL environment via /proc/version
- Use wsl-notify-send.exe for Windows notifications
- Add setup wizard option to install wsl-notify-send
fix: handle non-git directories on Windows

- Wrap git commands in try-catch
- Check $LASTEXITCODE after git commands
- Fall back to folder name when not in git repo

Rules

  • No Co-Authored-By lines
  • No .env files
  • Run tests before committing
  • Keep messages concise but descriptive
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. 1mo ago First seen · 82 lines · 6 tokens per session scan A 94c4563e3bb6

Subscribe to this mod's changes

commit is a command published in the GitHub repository mylee04/code-notify (289 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 358 once invoked, about $0.0000 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-30.