netclaw: Command for Claude Code

.specify/extensions/git/commands/speckit.git.commit.md

speckit.git.commit is a command for Claude Code from automateyournetwork/netclaw. It costs 10 tokens per session (426 once invoked), scanned A, a copy of speckit.git.commit, Apache-2.0.

A Git command that stages and commits project changes automatically when configured hook events occur. A commit is a saved set of changes in Git history.

In plain words
What is it for?
Create commits after or before configured Spec Kit commands, using configured or default messages.
Why use it?
It reduces the need to remember to save completed workflow changes manually, while only acting for enabled events.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

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

Reuse

Borrowing it

Nothing to install: this file belongs to automateyournetwork/netclaw. 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/automateyournetwork/netclaw/main/.specify/extensions/git/commands/speckit.git.commit.md
Clone the repo
git clone --depth 1 https://github.com/automateyournetwork/netclaw

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/commands/automateyournetwork/netclaw/speckit.git.commit/github.svg)](https://agentmods.dev/commands/automateyournetwork/netclaw/speckit.git.commit)
Your own site
<a href="https://agentmods.dev/commands/automateyournetwork/netclaw/speckit.git.commit"><img src="https://agentmods.dev/badge/commands/automateyournetwork/netclaw/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/commands/automateyournetwork/netclaw/speckit.git.commit"><img src="https://agentmods.dev/badge/commands/automateyournetwork/netclaw/speckit.git.commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 426 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.00010 $0.00426
Opus 5.5 $0.00004 $0.00170
Sonnet 5.5 $0.00002 $0.00085
Haiku 4.5 $0.00001 $0.00043

Measured 27d ago against content hash 445ed4cd43c8, 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 27d 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 — 47 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.

.specify/extensions/git/commands/speckit.git.commit.md · 49 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. 27d ago First seen · 49 lines · 10 tokens per session scan A 445ed4cd43c8

Subscribe to this mod's changes

speckit.git.commit is a command published in the GitHub repository automateyournetwork/netclaw (715 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 426 once invoked, about $0.0000 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 47 lines, and is treated as a copy.

Related

speckit.git.commit compared with commands from other repositories

speckit.git.commit next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
speckit.git.commitautomateyournetwork/netclawCommand715yesterdayApache-2.0A10Claude Code
standupvvedantb/evaCommand101yesterdayMITA0Claude Code
gitazrtydxb/procoderCommand21111d agoApache-2.0A20Claude Code
session-reportdamusix/atomic-claudeCommand1154d agoMITA31Claude Code
commitechoVic/blade-codeCommand18124d agoMITA8Claude Code
git-workflowHermeticOrmus/LibreUIUX-Claude-CodeCommand1151mo agoMITA14Claude Code
commitjoaquimscosta/arkhe-claude-pluginsCommand2221d agoMITA11Claude Code