Borrowing it
Nothing to install: this file belongs to jd-solanki/airig. 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/jd-solanki/airig/main/.ai/skills/automate-commit-based-gh-release-changelog/SKILL.mdgit clone --depth 1 https://github.com/jd-solanki/airigWrote 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/jd-solanki/airig/automate-commit-based-gh-release-changelog)<a href="https://agentmods.dev/skills/jd-solanki/airig/automate-commit-based-gh-release-changelog"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/automate-commit-based-gh-release-changelog/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/jd-solanki/airig/automate-commit-based-gh-release-changelog"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/automate-commit-based-gh-release-changelog.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.00080 | $0.00448 |
| Opus 5 | $0.00040 | $0.00224 |
| Sonnet 5 | $0.00016 | $0.00090 |
| Haiku 4.5 | $0.00008 | $0.00045 |
Grade A, and why
automate-commit-based-gh-release-changelog 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 10d 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.
What it actually says
Automate Commit-Based GitHub Release Changelog
Uses changelogithub to read Conventional Commits between tags and create (or update) a GitHub release with a formatted changelog.
Workflow setup
Trigger and permissions
on:
push:
tags:
- 'v*'
permissions:
contents: write # required — default contents:read cannot create releases
Changelog step
Run changelogithub as the last step — after npm publish (if any) — so a failed publish doesn't create a dangling GitHub release:
- uses: actions/checkout@v6
with:
fetch-depth: 0 # full tag history required; shallow clone produces empty changelog
- name: Generate changelog
run: npx changelogithub
env:
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
Conventional Commits
changelogithub groups entries by type and surfaces breaking changes at the top:
| Commit prefix | Changelog section |
|---|---|
feat: |
Features |
fix: |
Bug Fixes |
chore: |
Chores |
feat!: / chore!: |
Breaking Changes (top) |
Commits that don't follow the convention are omitted from the changelog.
Preview before pushing a tag
npx changelogithub --dry
Reference
- For a complete end-to-end workflow combining npm publish + changelog generation, see
automate-npm-release/EXAMPLE_WORKFLOW.ymlif that skill is installed locally.
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.
- 10d ago First seen · 62 lines · 80 tokens per session scan A cad867a8710b
automate-commit-based-gh-release-changelog is a skill published in the GitHub repository jd-solanki/airig (2 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 448 once invoked, about $0.0004 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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.