A tool-guided workflow for creating a Conventional Commit from the current Git changes. Conventional Commits use labels such as `feat` or `fix` to describe the kind of change.

Use it when you want to analyze staged or unstaged changes, choose a commit type and scope, and create the commit.

It removes the need to inspect the diff and work out the commit format manually. The resulting message follows the required structure.

How ryanmichaeljames/dataverse-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ryanmichaeljames/dataverse-mcp. 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/ryanmichaeljames/dataverse-mcp/main/.claude/skills/git-commit/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ryanmichaeljames/dataverse-mcp

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/ryanmichaeljames/dataverse-mcp/git-commit/github.svg)](https://agentmods.dev/skills/ryanmichaeljames/dataverse-mcp/git-commit)

Your own site

<a href="https://agentmods.dev/skills/ryanmichaeljames/dataverse-mcp/git-commit"><img src="https://agentmods.dev/badge/skills/ryanmichaeljames/dataverse-mcp/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ryanmichaeljames/dataverse-mcp/git-commit"><img src="https://agentmods.dev/badge/skills/ryanmichaeljames/dataverse-mcp/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,082 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.00035	$0.01082
Opus 5.5	$0.00014	$0.00433
Sonnet 5.5	$0.00007	$0.00216
Haiku 4.5	$0.00003	$0.00108

Measured 1mo ago against content hash 665e7433c3cc, 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 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/skills/git-commit/SKILL.md · 119 lines

How it starts

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

Git Commit — Conventional Commits v1.0.0

Specification

Commits must be prefixed with a type (a noun: feat, fix, etc.), optional scope, optional !, then a required colon and single space.
feat must be used when a commit introduces a new feature (SemVer MINOR).
fix must be used when a commit patches a bug (SemVer PATCH).
A scope may follow the type as a noun in parentheses: fix(parser):.
The description must immediately follow the colon-space: feat: add login.
A body may follow after one blank line; it is free-form and may span multiple paragraphs.
One or more footers may follow after one blank line; each has a token, a separator (: or #), and a value.
Footer tokens use hyphens for internal whitespace except for the special token BREAKING CHANGE.
Footer values may contain spaces and newlines.
Breaking changes must be indicated either in the footer (BREAKING CHANGE: <desc>) or with ! before the colon.
BREAKING CHANGE in a footer must be uppercase (SemVer MAJOR).
BREAKING-CHANGE is synonymous with BREAKING CHANGE as a footer token.
Types beyond feat and fix are permitted; recommended set below.
All parts are case-insensitive except BREAKING CHANGE, which must remain uppercase.
! may be appended to any type/scope to draw attention to a breaking change (can appear alongside a BREAKING CHANGE footer).

Format

<type>[(<scope>)][!]: <description>

[body]

[footer(s)]

Commit types

Type	Purpose	SemVer impact
`feat`	New feature	MINOR
`fix`	Bug fix	PATCH
`build`	Build system or external dependency change	–
`chore`	Maintenance tasks not touching src/tests	–
`ci`	CI pipeline / config changes	–
`docs`	Documentation only	–
`perf`	Performance improvement	–
`refactor`	Code change that is neither feat nor fix	–
`revert`	Reverts a previous commit	–
`style`	Formatting, whitespace (no logic change)	–
`test`	Add or update tests	–

Read the full file on GitHub · 119 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 First seen · 119 lines · 35 tokens per session scan A 665e7433c3cc

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository ryanmichaeljames/dataverse-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,082 once invoked, about $0.0001 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

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

davidondrej/skills · 25 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

dataverse-mcp: Skill for Claude Code