Enforce CHANGELOG.md release-note structure with a 10-block rolling window.
npx skills add https://github.com/jonaseck2/slaktforskning --skill oss-release
Please help me install this Agent Skill. Skill: oss-release Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/oss-release Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill oss-release
This Skill prevents inconsistent, bloated, or forgotten release documentation by enforcing a strict CHANGELOG.md block structure that matches the automated CI-based release flow.
Use oss-release while editing CHANGELOG.md during a version-bumped commit to produce a correctly formatted, rolling-window release entry.
High-intent search queries and answers about installing and using this skill.
To keep CHANGELOG release notes consistent for automated GitHub releases, enforce a strict block structure that matches your CI-driven flow, ensuring each version-bumped commit prepends exactly one correctly formatted, readable block.
The best way to format a CHANGELOG.md entry for a version bump is using bullet-style constraints that maintain readability for non-developers, intentionally avoiding engineering-detail bloat while adhering to one block per commit.
To archive older changelog entries without breaking CI versioning, maintain a 10-block rolling window in your primary CHANGELOG.md and move older entries to an archive file, keeping a stable footer pointer linking to the archived history.
Your automated OSS release process produces inconsistent documentation because it lacks strict structural enforcement, allowing unregulated entries; applying release-discipline rules ensures documentation matches the CI-driven GitHub Release process consistently.
Yes, you can use a rolling window approach for CHANGELOG management in open source projects by keeping only the 10 most recent version blocks active and archiving the rest, which prevents file bloat while preserving historical accessibility.
You should not use bullet-style constraints for changelog entries if your audience requires detailed engineering logs, as these constraints specifically filter out engineering-detail bloat to keep release notes readable for non-developers.
maslennikov-igGenerate Keep a Changelog–compliant Markdown sections from git commits, plan files, or manual entries.
nickromneyAutomate version bumps, changelog updates, and publishing from conventional commits.
ffalorAutomates commit messages conforming to conventional specifications.
utkudarilmazGenerate CHANGELOG.md and release notes from git history.
