commit

A workflow for staging changes and creating a Git commit with a standard format. A commit is a saved checkpoint in a Git project.

In plain words
What is it for?
Use it to review current changes, choose which files to include, and create a correctly formatted commit.
Why use it?
It helps keep commits focused, consistently named, and free of accidental secrets or unfinished work.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/evermind-ai/everos/commit
Any agent
npx skills add EverMind-AI/EverOS --skill commit
Clone the repo
git clone --depth 1 https://github.com/EverMind-AI/EverOS

Made for: Claude Code, Codex.

Per session 14 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. Scan, not verified.
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 $0.00014 $0.00472
Opus 5 $0.00007 $0.00236
Sonnet 5 $0.00003 $0.00094
Haiku 4.5 $0.00001 $0.00047

Measured yesterday against content hash 86365f623471, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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/commit/SKILL.md · 55 lines

What it actually says

/commit

Create a well-formed commit following the Conventional Commits standard. The format is enforced by gitlint in the commit-msg hook.

Steps

  1. Run git status and git diff (and git diff --staged) to see what changed.

  2. Review recent history for style: git log --oneline -10.

  3. Group the change into a single focused commit. If the working tree mixes unrelated changes, stage selectively (git add -p / specific paths) rather than committing everything at once.

  4. Write the message in Conventional Commits form:

    <type>[(scope)][!]: <imperative summary, ≤72 chars>
    
    <optional body: what & why, wrapped at 72>
    
    <optional footer: BREAKING CHANGE: …, Refs: #123>
    
  5. Never use --no-verify. If pre-commit hooks fail, fix the cause and re-commit.

  6. Do not commit secrets, generated artifacts, or work-in-progress directly to the protected main branch.

Types

Type Use for
feat new feature
fix bug fix
refactor behavior-preserving restructure
test add / update tests
docs documentation
style formatting only
perf performance
chore config / build / tooling
build build system or dependencies
ci CI configuration
revert revert a previous commit

Notes

  • No emoji — the title must start with the type.
  • One logical change per commit; keep the history bisectable.
  • The summary is imperative mood: "add", not "added" / "adds".
  • scope is optional: fix(search): …. A ! before the colon (or a BREAKING CHANGE: footer) marks a breaking change.
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. yesterday First seen · 55 lines · 14 tokens per session scan A 86365f623471

Subscribe to this mod's changes

commit is a skill published in the GitHub repository EverMind-AI/EverOS (12,594 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 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-30.

Related

Other skills, from other repositories

salesforce

Query and manage Salesforce CRM data via the Salesforce CLI (sf). Run SOQL/SOSL queries, inspect object schemas, create/update/delete records, bulk import/export, execute Apex, deploy metadata, and make raw REST API calls.

jdrhyne/agent-skills · 50 tokens

nutrient-openclaw

Use the pinned Nutrient OpenClaw plugin to convert, OCR, extract, redact, watermark, sign, or inspect the last-known local credit record for documents. Route only OpenClaw document-processing requests to its declared tools. Treat processing as an external, credit-consuming DWS transfer that requires a bounded estimate…

jdrhyne/agent-skills · 77 tokens

command-creator

This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.

jdrhyne/agent-skills · 66 tokens

gallery-scraper

Bulk download images from login-protected gallery websites using an attached browser session. Use when asked to scrape, download, or save images from authenticated gallery pages, extract full-size images from thumbnails, or batch download from multi-page galleries.

jdrhyne/agent-skills · 51 tokens

todo-tracker

Persistent TODO scratch pad for tracking tasks across sessions. Use when the user asks to add, list, complete, remove, or summarize tasks in a portable workspace Markdown file. Uses stable task IDs and exact matching; heartbeat reporting is opt-in and count-only.

jdrhyne/agent-skills · 55 tokens

frontend-design

Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.

jdrhyne/agent-skills · 28 tokens