cli-git-conventional

A set of rules for Git and Jujutsu, tools for tracking code changes, commits, branches, and releases. It follows Conventional Commits and Semantic Versioning, which standardize change descriptions and version numbers.

In plain words
What is it for?
Creating commits, branches, tags, changelogs, and version bumps, plus auditing directories for unwanted markers.
Why use it?
It keeps repository history and release information consistent and checks files for prohibited AI-related markers.

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/destynova2/cli-code-skills/cli-git-conventional
Any agent
npx skills add Destynova2/cli-code-skills --skill cli-git-conventional
Clone the repo
git clone --depth 1 https://github.com/Destynova2/cli-code-skills

Made for: Claude Code, Codex.

Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,267 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.00128 $0.05267
Opus 5 $0.00064 $0.02634
Sonnet 5 $0.00026 $0.01053
Haiku 4.5 $0.00013 $0.00527

Measured 2d ago against content hash 08ab8fd717a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli-git-conventional 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 2d 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.

cli-git-conventional/SKILL.md · 495 lines

How it starts

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

Optimization: This skill uses on-demand loading. SemVer rules, git/jj commands, and branch conventions live in references/.

Language rule: Commit messages are always in the project's commit language (check git log --oneline -10). If mixed, default to English. The skill instructions are bilingual (FR/EN) but output follows the project.

Conventional Commits -- Ghostwriter

"A commit message is a letter to your future self. Write it in your voice, not a machine's."

Reference: https://www.conventionalcommits.org/en/v1.0.0/

Rule zero: Authorship

NEVER add Co-authored-by: Claude or any AI trailer. The commit belongs entirely to the person who asked. No Co-authored-by, Generated-by, AI-assisted, or equivalent trailers. Ever.

Ghost mode

When the user says /ghost (the only slash-command spelling), not an AI, I'm not an AI, pas une IA, or equivalent natural language, enforce maximum ghostwriter discipline:

  • Write as the user's quiet maintainer, not as an assistant.
  • Do not mention AI, agents, prompts, models, Claude, Codex, ChatGPT, OpenAI, or Anthropic in commits, branches, tags, changelogs, PR text, release notes, or generated repo files unless the repository itself is explicitly about those tools.
  • Prefer direct project vocabulary over meta-process language.
  • If a requested message contains AI markers, rewrite it before committing.
  • Run the full-directory AI marker audit. In ghost mode, staged marker entries are not allowed to remain unless reclassified as product-fixture with a short reason tied to source, tests, packaging, or documented product behavior.
  • For outbound prose (emails, messages, relances), the same ghostwriter discipline lives in cli-forge-plume with a conversational AI-tells catalog.

Ghostwriter style

Claude is the ghostwriter. The message is signed by the user, written in their voice.

Bad (AI voice) Good (human voice)
feat: implement comprehensive solution for handling edge cases in authentication module feat(auth): handle token expiry on refresh
refactor: enhance code quality and maintainability by restructuring refactor(router): split dispatch logic into smaller fns
fix: resolve critical issue that was causing unexpected behavior fix(cache): prevent stale reads after TTL reset
chore: update various dependencies to their latest versions chore(deps): bump tokio 1.35 -> 1.37

Read the full file on GitHub · 495 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.

  1. 2d ago First seen · 495 lines · 128 tokens per session scan A 08ab8fd717a3

Subscribe to this mod's changes

cli-git-conventional is a skill published in the GitHub repository Destynova2/cli-code-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 128 tokens to every session and 5,267 once invoked, about $0.0006 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-31.