What is semantic-git?

A workflow for preparing and organizing Git commits, where Git is a system for tracking changes to files. It uses conventional commit messages and keeps each commit focused on related changes.

Use it when staging files, grouping implementation with its tests, writing commit messages, preparing commits, or getting ready to push changes.

It helps make project history easier to understand and avoids mixing unrelated edits in one commit.

semantic-git — Skill for Claude Code and Codex by siviter-xyz: A workflow for preparing and organizing Git commits, where…

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/siviter-xyz/dot-agent/semantic-git

Any agent

npx skills add siviter-xyz/dot-agent --skill semantic-git

Clone the repo

git clone --depth 1 https://github.com/siviter-xyz/dot-agent

Made for: Claude Code, Codex.

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/siviter-xyz/dot-agent/semantic-git.svg)](https://agentmods.dev/skills/siviter-xyz/dot-agent/semantic-git)

Your own site

<a href="https://agentmods.dev/skills/siviter-xyz/dot-agent/semantic-git"><img src="https://agentmods.dev/badge/skills/siviter-xyz/dot-agent/semantic-git.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,497 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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.01497
Opus 5	$0.00016	$0.00749
Sonnet 5	$0.00007	$0.00299
Haiku 4.5	$0.00003	$0.00150

Measured 6d ago against content hash 2854a95f7df2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

semantic-git 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 6d 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.

skills/semantic-git/SKILL.md · 184 lines

How it starts

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

Semantic Git

Manage Git commits using conventional commit format with atomic commits and concise messages.

This skill is zagi-aware and is designed to work well with AI IDEs (Cursor, etc.)

Tooling

Preferred: zagi (a better git interface for agents).
- Assume zagi is installed if:
  - git is aliased to zagi in the shell or
  - a zagi binary is available.
- When in doubt, treat git as if it may be zagi-compatible and avoid using exotic flags.
- Even when zagi is available, generate plain git commands and let any git → zagi integration handle them.
Fallback: plain git when zagi is not available.

When to Use

Committing changes to git
Staging files for commit
Creating commit messages
Managing atomic commits
Before pushing changes

Core Principles

Atomic commits: Stage and commit related changes together. Tests go with implementation code.
User confirmation: Always confirm with user before committing and before moving to the next commit.
Conventional format: Use conventional commit message format (feat, fix, etc.) unless directed otherwise.
Concise messages: Keep messages brief and to the point. Omit description unless change is complicated.
Command transparency: Always show the exact git commands that will be run (which may be handled by zagi via alias/wrapper), and ask whether the user wants:
- to run them manually, or
- to have the agent run them.

Commit Message Format

<type>[optional scope]: <subject>

[optional body]

[optional footer(s)]

Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies
ci: Changes to CI configuration files and scripts
chore: Maintenance tasks (updating build tasks, dependencies, etc.; no production code change)
revert: Revert a previous commit

Read the full file on GitHub · 184 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

6d ago First seen · 184 lines · 33 tokens per session scan A 2854a95f7df2

Subscribe to this mod's changes

semantic-git is a skill published in the GitHub repository siviter-xyz/dot-agent (21 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,497 once invoked, about $0.0002 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.

Commits Git and workflow

create-pr

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

prisma/orm · 47 tokens

git-commit

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

ThinkInAIXYZ/deepchat · 15 tokens

commit-push-pr

Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.

GCWing/BitFun · 68 tokens

mcore-split-pr

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

NVIDIA/skills · 25 tokens

commit

Commit current changes with a clear, descriptive message.

NVIDIA-NeMo/DataDesigner · 11 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