Borrowing it
Nothing to install: this file belongs to brianmontanaweb/agentic-design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brianmontanaweb/agentic-design-system/main/.claude/skills/commit-message/SKILL.mdgit clone --depth 1 https://github.com/brianmontanaweb/agentic-design-systemWrote 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.
[](https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/commit-message)<a href="https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/commit-message"><img src="https://agentmods.dev/badge/skills/brianmontanaweb/agentic-design-system/commit-message/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.
<a href="https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/commit-message"><img src="https://agentmods.dev/badge/skills/brianmontanaweb/agentic-design-system/commit-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00051 | $0.00738 |
| Opus 5.5 | $0.00020 | $0.00295 |
| Sonnet 5.5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
commit-message 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message
Draft a commit message for the current changes given $ARGUMENTS (optional: --commit to also create the commit).
Gotchas
- Draft-only by default — output the message; do not run
git commitunless--commitwas passed. - Staged changes win — if anything is staged, describe only the staged diff; otherwise describe all uncommitted changes (and say which set you used).
- Match history, not a generic convention — read recent
git logsubjects before writing; this repo's style is authoritative over any general conventional-commits habit. - Never invent scope from a single stray file — scope reflects where the substance of the change lives; a drive-by fix in a second area goes in the body, not the scope.
Step 1 — Collect the change
git status --short
git diff --staged --stat # if anything is staged
git diff --stat # otherwise
git log --oneline -15
Read the full diff (git diff --staged / git diff) for the files that carry the substance of the change. Skim generated files (packages/tokens/src/generated.ts, snapshots) — name them in the body if regenerated, but do not describe their contents line by line.
Step 2 — Choose type and scope
Format: type(scope): subject — scope omitted when the change is repo-wide.
| Type | Used for |
|---|---|
feat |
New component, prop, token, skill, or capability |
fix |
Bug or violation fix (a11y fixes count) |
refactor |
Restructuring with no behavior change |
chore |
Tooling, lint config, versioning, baselines |
test |
Test or eval additions/changes |
build |
Bundling, packaging, build order |
docs |
Spec docs or markdown-only changes |
Scopes seen in history: skills, lint, core, evals, plus package names (tokens, agents) and component names where the change is that narrow. Multi-part changes may join two clauses with ; in the subject (see 142a14c).
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.
- 2mo ago First seen · 65 lines · 51 tokens per session scan A fb7155c0ec47
commit-message is a skill published in the GitHub repository brianmontanaweb/agentic-design-system (3 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 738 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
seed-change
A workflow for assessing the impact of SEED changes, preparing package release notes called changesets, or carrying out an explicitly requested rebase, commit, push, and pull request. It separates planning from actions that change the repository or remote.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.
01-commit
Create atomic conventional commits; safely retry scoped hook fixes; optionally push. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release.
devflow
End-to-end development workflow for the Ambient Code Platform. Covers ticket → branch → spec → code → commit → PR → review → deploy → verify. Self-improving: update this skill whenever a failure path is discovered or a shortcut is validated. Git history is the audit trail.