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.
npx skills add rockscy/solo-skills --skill changelog-from-commitsgit clone --depth 1 https://github.com/rockscy/solo-skillsWrote 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/rockscy/solo-skills/changelog-from-commits)<a href="https://agentmods.dev/skills/rockscy/solo-skills/changelog-from-commits"><img src="https://agentmods.dev/badge/skills/rockscy/solo-skills/changelog-from-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.
<a href="https://agentmods.dev/skills/rockscy/solo-skills/changelog-from-commits"><img src="https://agentmods.dev/badge/skills/rockscy/solo-skills/changelog-from-commits.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.00055 | $0.01093 |
| Opus 5.5 | $0.00022 | $0.00437 |
| Sonnet 5.5 | $0.00011 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
changelog-from-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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog from Commits / 提交转更新日志
When to use
- The user is cutting a release and needs user-facing release notes.
- There is a clear range: a tag, a date, or a commit SHA to diff from.
- The audience is users, not contributors (Conventional Commits already exists for the latter).
When NOT to use
- The repo has no user-facing surface (internal libraries, scripts) — a commit log is fine.
- The range covers months of work. Break it into smaller releases first.
- The user wants a marketing post — that's launch-tweet, not a changelog.
Approach
- Get the raw commit list:
git log <prev-tag>..HEAD --pretty=format:"%h %s%n%b" --no-merges - Group commits into three buckets, in this order:
- Added — net-new user-visible capability.
- Changed / Fixed — behavior that users would notice.
- Internal — refactors, deps, docs (collapse into a single line at the bottom).
- Translate from dev-speak to user-speak.
- ❌ "refactor: extract validation middleware"
- ✅ (skip — internal)
- ❌ "fix: handle null in payment.processor"
- ✅ "Fixed a crash when applying coupons to gift cards."
- Drop noise. Typo fixes, README tweaks, CI tweaks, version bumps → cut.
- Each bullet is one sentence, past tense, user perspective.
- If a bullet needs more than one sentence, it deserves its own blog post — link out.
Output format
## v<version> — YYYY-MM-DD
### Added
- <bullet>
### Changed
- <bullet>
### Fixed
- <bullet>
### Internal
- <one-line summary>: deps bumped, tests added, docs polished.
Skip empty sections entirely.
Worked example
Input commits:
a1b2c3d feat: add CSV export to reports
e4f5g6h fix: correct rounding in monthly totals
1a2b3c4 chore: bump axios to 1.7.5
9z8y7x6 refactor: split UserService
5d4c3b2 docs: fix typo in README
abcdef0 feat: dark mode toggle
Output:
## v1.4.0 — 2026-04-30
### Added
- CSV export for any report — find it in the report toolbar.
- Dark mode toggle in Settings → Appearance.
### Fixed
- Monthly totals now round consistently with daily totals (off-by-1¢ on edge cases).
### Internal
- Dependency updates and a service refactor; no user impact expected.
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.
- 1mo ago First seen · 127 lines · 55 tokens per session scan A b6104ec4d9fb
changelog-from-commits is a skill published in the GitHub repository rockscy/solo-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 1,093 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
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.