agentmods.dev

managing-commits

managing-commits is a skill for Claude Code from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 66 tokens per session (5,653 once invoked), scanned A, original, MIT.

A guide for writing and reviewing Git commit messages, which describe saved changes in a project's history. It covers conventional commits, commit quality, history analysis, and issue references.

In plain words
What is it for?
Use it when creating commit messages, checking commit quality or history, using conventional commits, or linking commits to issues.
Why use it?
It helps make the project history easier to understand and supports tools that use consistent commit formats.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the github-workflows plugin — 8 skills, 9 commands, 4 agents shipped together

not rated 3repo 6mo ago A scan 66 tokens original MIT

Good fit Use it when creating commit messages, checking commit quality or history, using conventional commits, or linking commits to issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits
View source ↗ C0ntr0lledCha0s/claude-code-plugin-automations
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.

Any agent
npx skills add C0ntr0lledCha0s/claude-code-plugin-automations --skill managing-commits
Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code.

Or install github-workflows, the plugin that ships this one along with the rest of its 8 skills, 9 commands, 4 agents.

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 managing-commits

README.md
[![agentmods](https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits/github.svg)](https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits)
Your own site
<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits/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 managing-commits

Your own site · 80×15
<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,653 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 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.1 $0.00066 $0.05653
Opus 5 $0.00033 $0.02826
Sonnet 5 $0.00013 $0.01131
Haiku 4.5 $0.00007 $0.00565

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

Security

Grade A, and why

managing-commits 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 9d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/commit-analyzer.py, scripts/conventional-commits.py, scripts/group-files.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

github-workflows/skills/managing-commits/SKILL.md · 912 lines

How it starts

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

Managing Commits Skill

You are a Git commit management expert specializing in conventional commits, commit quality, and git history analysis. You understand how well-structured commits improve project maintainability, enable automation, and facilitate collaboration.

When to Use This Skill

Auto-invoke this skill when the user explicitly:

  • Asks about commit message format ("how should I format my commit message")
  • Requests help writing commits ("help me write a commit", "create a commit message")
  • Mentions conventional commits ("should I use conventional commits")
  • Asks about commit quality ("review my commit messages", "are my commits good")
  • Wants commit history analysis ("analyze my commit history", "check my commits")
  • References /commit-smart, /commit-review, or /commit-interactive commands

Do NOT auto-invoke for casual mentions of "commit" in conversation (e.g., "I committed to finishing this feature"). Be selective and only activate when commit-related assistance is clearly needed.

Your Capabilities

  1. Commit Message Generation: Create well-structured conventional commit messages
  2. Commit Quality Analysis: Review commits for format, clarity, and consistency
  3. History Analysis: Analyze git history for patterns and issues
  4. Issue Integration: Link commits to GitHub issues with proper references
  5. Breaking Change Detection: Identify and document breaking changes
  6. Changelog Generation: Generate changelogs from commit history

Your Expertise

1. Conventional Commits Format

Standard structure:

<type>(<scope>): <subject>

<body>

<footer>

Types (from Angular convention):

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only changes
  • style: Formatting, missing semi colons, etc.
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Performance improvement
  • test: Adding or correcting tests
  • chore: Changes to build process or auxiliary tools
  • ci: Changes to CI configuration files and scripts
  • build: Changes that affect the build system or dependencies
  • revert: Reverts a previous commit

Read the full file on GitHub · 912 lines

Files

What ships with it

8 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. 9d ago First seen · 912 lines · 66 tokens per session scan A e88f8f4e8408

Subscribe to this mod's changes

managing-commits is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 66 tokens to every session and 5,653 once invoked, about $0.0003 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.

CommitsGit and workflow
Related

Other skills, from other repositories

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

mcore-split-pr

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

NVIDIA/skills · 25 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

strict-tdd

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

a5c-ai/babysitter · 34 tokens

git-commit

Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…

redai-infra/Relax · 73 tokens