git-commit

git-commit is a skill for Claude Code, Codex from Phaedra-Solutions/cursor-rules. It costs 65 tokens per session (978 once invoked), scanned A, original, MIT.

A guided Git commit workflow that reviews changes, drafts a commit message, checks staged files for secrets, and then creates the commit.

In plain words
What is it for?
Use it when you want to inspect staged work, follow the repository's commit convention, and create a focused commit.
Why use it?
It reduces accidental commits of unrelated files or credentials and gives the developer a chance to approve the message before saving changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when you want to inspect staged work, follow the repository's commit convention, and create a focused commit.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/phaedra-solutions/cursor-rules/git-commit
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 Phaedra-Solutions/cursor-rules --skill git-commit
Clone the repo
git clone --depth 1 https://github.com/Phaedra-Solutions/cursor-rules

Made for: Claude Code, Codex.

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 git-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/git-commit/github.svg)](https://agentmods.dev/skills/phaedra-solutions/cursor-rules/git-commit)
Your own site
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/git-commit"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/git-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 git-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/git-commit"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 978 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.00065 $0.00978
Opus 5.5 $0.00026 $0.00391
Sonnet 5.5 $0.00013 $0.00196
Haiku 4.5 $0.00006 $0.00098

Measured 3d ago against content hash 87892d92233c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-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 3d 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/git-commit/SKILL.md · 77 lines

How it starts

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

Git commit

When to use

  • The user asks you to commit, write a commit message, or "save this to git".

Never commit on your own initiative, even at the end of a task.

Before you start

  • Check the repo state with git status --short and the current branch with git branch --show-current.
  • If changes are already staged, the commit covers only those. If nothing is staged, ask which files to include; never stage unrelated changes or files you didn't touch without asking.
  • Check for a project commit convention (Conventional Commits, commitlint.config.*, a CONTRIBUTING.md section, a commit template). If one exists, follow it and keep the dash-list body below the required header. Otherwise use the format below.

Steps

  1. Inspect the changes with git. Read the actual diff, not just file names:

    git diff --staged --stat
    git diff --staged
    

    (Use git diff for unstaged changes the user wants to include, after they confirm.)

  2. Make notes of what changed, grouped by intent rather than by file.

  3. Draft the message as a dash list, one line per change:

    • concise, in present tense ("Add", "Fix", "Remove", not "Added" or "Adds");
    • focused on what changed, not how you did it;
    • short lines; keep the whole message small. Split unrelated work into separate commits instead of one long message.
  4. Show the message as plain text and ask for approval. Show only the message, not the command:

    - Add rate limiting to the login endpoint
    - Fix the empty-state message on the orders page
    - Remove the unused date helper
    

    Wait for the user to approve or edit it.

  5. Scan staged files for secrets if gitleaks is installed (see secrets-scan):

    gitleaks git --staged --redact --no-banner -v
    

    If it finds anything, stop, tell the user what and where (never the value), and follow secrets-scan. If gitleaks isn't installed, check the diff yourself for keys, tokens, passwords, .env files and private keys, and say that you did a manual check.

  6. Commit with the approved lines, one argument per line:

Read the full file on GitHub · 77 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. 3d ago First seen · 77 lines · 65 tokens per session scan A 87892d92233c

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository Phaedra-Solutions/cursor-rules (4 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 978 once invoked, about $0.0003 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-11-01.