Menu
Generate release notes from merged pull requests. Use when preparing a tagged release.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Scores the authoring quality of Claude Code skill bundles. Analyzes SKILL.md and supporting documentation across ten deterministic dimensions — metadata completeness, information density, lexical diversity, readability, topic coverage, structural coherence, code maintainability, example quality, progressive disclosure, and behavioral configuration — and returns a 0–100 score with per-dimension breakdowns.
Reconcile supplier invoices against purchase orders and flag variances. Use when a finance analyst uploads a PDF invoice batch, when quarterly accruals need vendor-level validation, or when a three-way match fails. Do not use for expense reports, payroll runs, or credit-note issuance — those follow separate approval chains.
A skill for processing things with the processor tool
Parses invoices and extracts totals, line items, and vendor details from PDFs.
does stuff
| name | calib-typical |
| description | Generate release notes from merged pull requests. Use when preparing a tagged release. |
Collect merged pull requests since the previous tag and group them into a changelog. The output follows the conventional-commits categories so downstream tooling can parse it.
Read the git history between the previous tag and HEAD. For each merge commit, resolve the pull request number and fetch its title and labels. Titles that follow the conventional prefix convention are grouped automatically; anything else lands in a miscellaneous bucket that a human reviews before publishing.
Labels take precedence over title prefixes when the two disagree, because maintainers relabel more often than they rewrite commit subjects.
Features, fixes, performance work, documentation, and internal chores each get their own section. Breaking changes are hoisted to the top regardless of their category, with the migration note extracted from the pull request body.
The generated file is markdown with one heading per category and one bullet per pull request, each linking back to the originating discussion. See notes.md for the label mapping table.
generate-release-notes --from v1.4.0 --to HEAD > CHANGELOG-v1.5.0.md
The command prints a summary of how many pull requests landed in each category so you can spot a mis-grouped entry before publishing.