commit-message

A skill for generating a structured commit message from staged code changes. A commit message briefly records what a saved change does.

In plain words
What is it for?
Use it when staged changes are ready to commit and you need a suitable summary.
Why use it?
It helps describe changes consistently without having to write the message from scratch.

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/paritytech/polkadot-ios-community/commit-message
Any agent
npx skills add paritytech/polkadot-ios-community --skill commit-message
Clone the repo
git clone --depth 1 https://github.com/paritytech/polkadot-ios-community

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 258 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00258
Opus 5 $0.00007 $0.00129
Sonnet 5 $0.00003 $0.00052
Haiku 4.5 $0.00001 $0.00026

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

Security

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 3d 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.

.claude/plugins/polkadotapp-workflows/skills/commit-message/SKILL.md · 37 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 37 lines · 14 tokens per session scan A d04947b29402

Subscribe to this mod's changes

commit-message is a skill published in the GitHub repository paritytech/polkadot-ios-community (5 stars, last pushed 3d ago), licensed GPL-3.0. It adds 14 tokens to every session and 258 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-31.

Related

Other skills, from other repositories

feature-specs

Maintain feature spec READMEs and the Feature Map index. Use when creating a new feature or aggregate, materially changing the behaviour of an existing one, writing or updating a spec README, or when asked about feature documentation coverage.

novasamatech/nova-spektr · 49 tokens

verify

Runtime-verify a renderer change by driving the app in a browser — build/launch/drive recipe for Nova Spektr.

novasamatech/nova-spektr · 27 tokens

search-patterns

Use when adding, changing or reviewing a user-typed search/filter over a list (accounts, wallets, contacts, validators, operations, assets) — a search input, combobox or picker filtering rows by query. Also use when a user reports search "not finding" an item they can see in the list, or results disappearing while…

novasamatech/nova-spektr · 76 tokens

conventional-commits

Conventional Commits specification for consistent, machine-readable git commit messages. Use when crafting commit messages, enforcing commitlint rules, or generating changelogs/releases.

pdsuwwz/chatgpt-vue3-light-mvp · 38 tokens

git-commit

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…

devantler-tech/ksail · 87 tokens

developer

Feature development for this repo — XP, DDD, BDD, TDD, Glossary naming, Apple HIG minimal UX, living docs sync (C4 / Glossary / User Story Map), and mandatory commit/PR standards (why body + References from official docs and research). Use when implementing features, writing tests, committing, opening PRs, UI work, or…

felixzhu97/explore-chat · 91 tokens