DevOps & Infra Skill
Bash Defensive Patterns
Master defensive Bash programming techniques for production-grade scripts.
$15
Changelog Automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog…
Changelog Automation sets up an end-to-end release workflow that generates changelogs, release notes and version bumps automatically from your commit history, following the Keep a Changelog format and Semantic Versioning. It enforces Conventional Commits so every commit becomes a parseable, machine-readable changelog entry, then wires up the tooling that turns those commits into polished release notes. The hours your team spends hand-writing release notes disappear, and version numbers stop being guesswork.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category DevOps & Infra
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
The concrete pipeline the skill wires up so changelogs write themselves from commit history:
- Enforces Conventional Commits at the source: commitlint plus a husky commit-msg hook rejects anything outside the type-enum (feat, fix, perf, refactor and friends) or over the 72-character subject limit, so the changelog input is clean before automation starts.
- Picks the generator that fits the stack: semantic-release for fully automated npm releases, standard-version for manual-trigger bumps, git-cliff for fast Rust-based generation, commitizen for Python projects with version_files in pyproject.toml.
- Configures the commit-to-section mapping: feat becomes Features, fix becomes Bug Fixes, noise types (docs, chore, ci) are hidden, breaking changes flagged with ! or a BREAKING CHANGE footer force a MAJOR bump under SemVer.
- Dry-runs before anything irreversible: git cliff --dry-run or standard-version --dry-run previews the generated entries and the version bump, because a wrong tag pushed to a registry cannot be unpublished cleanly.
- Wires the release into CI: a GitHub Actions workflow runs the release on push to main, the release commit carries [skip ci] so it never re-triggers itself, and reruns on the same SHA stay idempotent (no duplicate tags or entries).
- Keeps a single source of truth: CHANGELOG.md is the authoritative record, version_files sync package.json or pyproject.toml with the git tag, and GitHub Release notes are generated from the changelog rather than written separately.
One power source. 6 lines out.
changelog-automation · core
core active · 6 lines
- ✓ standing up automated ch…
Standing up automated changelog and release-note generation
- ✓ enforcing conventional c…
Enforcing Conventional Commits with commitlint and husky
- ✓ semantic versioning bumps
Semantic versioning bumps from commit types
- ✓ github actions release p…
GitHub Actions release pipelines with semantic-release
- ✓ generating github and gi…
Generating GitHub and GitLab release notes
- ✓ maintaining a single cha…
Maintaining a single CHANGELOG.md as source of truth
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Reclaim the hours spent manually writing release notes every cycle
license: perpetual -
Version numbers that automatically reflect breaking, feature and fix changes
license: perpetual -
Idempotent release pipelines that never duplicate entries or tags
license: perpetual -
Consistent, professional release communication customers actually read
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Keep a Changelog formatted output with Added/Changed/Fixed/Security sections
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Engineering teams and maintainers who want release notes, versioning and changelogs generated automatically instead of written by hand.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
Will it work if my existing commits aren't already in Conventional Commits format?
Going forward it enforces the format with commitlint so new commits parse cleanly, but old freeform history won't auto-classify. For a backfilled changelog you either tag the past releases by hand or start the automation from the next version.
-
How does it decide whether a release is a patch, minor or major?
It reads the commit types: fixes drive a patch bump, features a minor one, and a breaking-change marker a major one, following Semantic Versioning. The version bump and the grouped notes both come from that same commit metadata.
-
Does it replace writing a real human release note?
It generates the structured changelog grouped by change type, which covers most routine releases. For a marketing-style launch narrative you still write that on top of the generated notes.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.