vocero-crm: Skill for Claude Code

.claude/skills/speckit-git-commit/SKILL.md

speckit-git-commit is a skill for Claude Code from kevinrivm/vocero-crm. It costs 18 tokens per session (472 once invoked), scanned A, a copy of speckit-git-commit, MIT.

A Spec Kit hook that stages and commits repository changes after a configured Spec Kit command or hook event. Its behavior is controlled by a Git configuration file.

In plain words
What is it for?
Use it to automatically commit changes after events such as specifying, planning, or implementing, when auto-commit is enabled.
Why use it?
It removes the repeated step of manually committing changes after supported Spec Kit actions. Commit behavior and messages can be configured per event or by default.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is kevinrivm/vocero-crm's own configuration. It tells Claude Code how to work on vocero-crm 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 vocero-crm configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kevinrivm/vocero-crm. 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/kevinrivm/vocero-crm/main/.claude/skills/speckit-git-commit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kevinrivm/vocero-crm

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kevinrivm/vocero-crm/speckit-git-commit"><img src="https://agentmods.dev/badge/skills/kevinrivm/vocero-crm/speckit-git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 472 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 100% copy Near-identical to another mod 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.00018 $0.00472
Opus 5.5 $0.00007 $0.00189
Sonnet 5.5 $0.00004 $0.00094
Haiku 4.5 $0.00002 $0.00047

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

Security

Grade A, and why

speckit-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 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.

Origin

This is a copy

100% identical to speckit-git-commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/speckit-git-commit/SKILL.md · 53 lines

What it actually says

Auto-Commit Changes

Automatically stage and commit all changes after a Spec Kit command completes.

Behavior

This command is invoked as a hook after (or before) core commands. It:

  1. Determines the event name from the hook context (e.g., if invoked as an after_specify hook, the event is after_specify; if before_plan, the event is before_plan)
  2. Checks .specify/extensions/git/git-config.yml for the auto_commit section
  3. Looks up the specific event key to see if auto-commit is enabled
  4. Falls back to auto_commit.default if no event-specific key exists
  5. Uses the per-command message if configured, otherwise a default message
  6. If enabled and there are uncommitted changes, runs git add . + git commit

Execution

Determine the event name from the hook that triggered this command, then run the script:

  • Bash: .specify/extensions/git/scripts/bash/auto-commit.sh <event_name>
  • PowerShell: .specify/extensions/git/scripts/powershell/auto-commit.ps1 <event_name>

Replace <event_name> with the actual hook event (e.g., after_specify, before_plan, after_implement).

Configuration

In .specify/extensions/git/git-config.yml:

auto_commit:
  default: false          # Global toggle — set true to enable for all commands
  after_specify:
    enabled: true          # Override per-command
    message: "[Spec Kit] Add specification"
  after_plan:
    enabled: false
    message: "[Spec Kit] Add implementation plan"

Graceful Degradation

  • If Git is not available or the current directory is not a repository: skips with a warning
  • If no config file exists: skips (disabled by default)
  • If no changes to commit: skips with a message
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. 2mo ago First seen · 53 lines · 18 tokens per session scan A 5c7bf976944f

Subscribe to this mod's changes

speckit-git-commit is a skill published in the GitHub repository kevinrivm/vocero-crm (419 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to speckit-git-commit, differing in 0 lines, and is treated as a copy.

Related

speckit-git-commit compared with skills from other repositories

speckit-git-commit next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
speckit-git-commitkevinrivm/vocero-crmSkill4194d agoMITA18Claude Code
create-prprisma/ormSkill48kyesterdayApache-2.0A48Claude Code, Codex
git-commitThinkInAIXYZ/deepchatSkill6.4kyesterdayApache-2.0A15Claude Code, Codex
repo-syncdavidondrej/skillsSkill4.3k3d agoMITA25Claude Code, Codex
engineer-bot-opsmakecindy/cindySkill9.3kyesterdayApache-2.0A57Claude Code, Codex
mcore-split-prNVIDIA/skillsSkill3.9kyesterdayApache-2.0A25Claude Code
git-commit-writermergisi/awesome-openclaw-agentsSkill4.1k2d agoMITA53Claude Code, Codex