What is prepare-commit-messages?

A skill for organizing uncommitted Git changes into feature-focused Conventional Commits, a standard format for commit messages.

Inspecting changes, grouping files into atomic commits, naming commits consistently, and identifying missing documentation updates.

It separates unrelated work, checks documentation needs, and prepares a reviewable commit plan before any commits are made.

How lsampaioweb/ai-instructions configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to lsampaioweb/ai-instructions. 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/lsampaioweb/ai-instructions/main/.cursor/skills/prepare-commit-messages/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/lsampaioweb/ai-instructions

Made for: Cursor.

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/lsampaioweb/ai-instructions/prepare-commit-messages/github.svg)](https://agentmods.dev/skills/lsampaioweb/ai-instructions/prepare-commit-messages)

Your own site

<a href="https://agentmods.dev/skills/lsampaioweb/ai-instructions/prepare-commit-messages"><img src="https://agentmods.dev/badge/skills/lsampaioweb/ai-instructions/prepare-commit-messages/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/lsampaioweb/ai-instructions/prepare-commit-messages"><img src="https://agentmods.dev/badge/skills/lsampaioweb/ai-instructions/prepare-commit-messages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 767 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.00088	$0.00767
Opus 5.5	$0.00035	$0.00307
Sonnet 5.5	$0.00018	$0.00153
Haiku 4.5	$0.00009	$0.00077

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

Security

Grade A, and why

prepare-commit-messages 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.

.cursor/skills/prepare-commit-messages/SKILL.md · 73 lines

How it starts

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

Logical Git Commits

Arguments

Optional path or feature-scope filter.
Omit the filter to cluster all uncommitted changes.

1. Inspect the Changes

Inspect git status, unstaged changes with git diff, and staged changes with git diff --cached.
Read the contents of untracked files listed by git status; they are part of the uncommitted work even though they do not appear in either diff.
Cluster all in-scope staged, unstaged, and untracked changes into atomic commits.

2. Resolution Rules

Sort order: Commit foundational changes (config, schemas, and dependencies) before feature layers.
Grouping Boundary: Group files strictly by feature domain (e.g., auth, payment).
Documentation Gate: If Markdown documentation exists for changed code but contains no corresponding updates, flag the affected docs and recommend running review-and-sync-docs before proceeding.
Commit Format: Use only Conventional Commits in this format: type(scope): description.
Scope Rule: Use a feature domain or infrastructure area.
Description: Write it in the imperative present tense, keep it to 50 characters or fewer, and do not end it with a period.
Body Rule: Document the why and the impact only.
Footer Rule: Append Closes #123 or tracking IDs if detected in branch or context.
Post-approval: Run git add and git commit sequentially for each cluster.

3. Safety Guards

Execution boundary: Apply changes only after the user confirms the commit plan.
Ask for Confirmation: Output: Proceed with executing this automated commit sequence? [yes/no]
Exit Code Check: Confirm the exit code is 0 after each git commit before staging the next cluster.
Scope Discipline: Never use technical-layer identifiers for grouping or as the commit scope.
Body Discipline: Never list modified files or duplicate diff data in the commit body.
Domain Boundary: If files in a cluster span more than one feature domain, flag the cluster and stop.
Type Discipline: Use a recognized Conventional Commit type; do not invent a repository-specific type without documenting it as an allowed type.

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

1mo ago Changed · +3 lines d13934f351cd
1mo ago Changed · +22 tokens per session b3e6c9d54915
1mo ago Changed 55a69e4789a2
2mo ago First seen · 70 lines · 66 tokens per session scan A 38052458c9ab

Subscribe to this mod's changes

prepare-commit-messages is a skill published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 5d ago), licensed MIT. It adds 88 tokens to every session and 767 once invoked, about $0.0004 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.

Commits Git and workflow

prepare-commit-messages next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
prepare-commit-messageslsampaioweb/ai-instructions	Skill	1	5d ago	MIT	A	88	Cursor
create-prprisma/orm	Skill	48k	yesterday	Apache-2.0	A	48	Claude Code, Codex
git-commitThinkInAIXYZ/deepchat	Skill	6.4k	yesterday	Apache-2.0	A	15	Claude Code, Codex
repo-syncdavidondrej/skills	Skill	4.3k	3d ago	MIT	A	25	Claude Code, Codex
engineer-bot-opsmakecindy/cindy	Skill	9.3k	today	Apache-2.0	A	57	Claude Code, Codex
mcore-split-prNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	25	Claude Code
git-commit-writermergisi/awesome-openclaw-agents	Skill	4.1k	2d ago	MIT	A	53	Claude Code, Codex

ai-instructions: Skill for Cursor