Astrumon/changelog-generator
.claude/skills/changelog-generator/SKILL.md
Use this skill to generate CHANGELOG entries from git commit history following Conventional Commits and Keep a Changelog format. Triggers on "generate changelog", "release notes", "what changed in v", or before creating a release tag.
development
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add Astrumon/Spovishun changelog-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 3:03 AM53.2s1 file scanned
SKILL.md
- name:
- changelog-generator
- description:
- Use this skill to generate CHANGELOG entries from git commit history following Conventional Commits and Keep a Changelog format. Triggers on "generate changelog", "release notes", "what changed in v", or before creating a release tag.
Changelog Generator
Overview
Use this skill to produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic bump logic, and changelog rendering.
Core Capabilities
- Parse commit messages using Conventional Commit rules
- Detect semantic version bump (
major,minor,patch) from commit stream - Render Keep a Changelog sections (
Added,Changed,Fixed, etc.) - Enforce commit format discipline
When to Use
- Before publishing a release tag
- During CI to generate release notes automatically
- When converting raw git history into user-facing notes
Conventional Commit Rules
Supported types:
feat,fix,perf,refactor,docs,test,build,ci,choresecurity,deprecated,remove
Breaking changes:
type(scope)!: summary- Footer/body includes
BREAKING CHANGE:
SemVer mapping:
- breaking →
major - non-breaking
feat→minor - all others →
patch
Changelog Format (Keep a Changelog)
# Changelog
## [Unreleased]
## [1.2.0] - 2026-03-22
### Added
- feat(bot): add /ping command for group mentions (#12)
### Fixed
- fix(db): resolve NPE when user not found in repository (#11)
### Changed
- refactor(service): extract notification logic into NotificationService
## [1.1.0] - 2026-03-01
...
Manual Generation (git log)
# List commits for a range
git log v1.1.0..HEAD --pretty=format:"%s" --no-merges
# Group by type manually
git log v1.1.0..HEAD --pretty=format:"%s" --no-merges | grep "^feat"
git log v1.1.0..HEAD --pretty=format:"%s" --no-merges | grep "^fix"
Common Pitfalls
- Mixing merge commit messages with release commit parsing
- Using vague commit summaries that cannot become release notes
- Failing to include migration guidance for breaking changes
- Treating
docs/chorechanges as user-facing features - Overwriting historical changelog sections instead of prepending
Best Practices
- Keep commits small and intent-driven
- Scope commit messages (
feat(api): ...) for multi-area repos - Review generated markdown before publishing
- Tag releases only after changelog is approved
- Keep an
[Unreleased]section for manual curation
Output Quality Checks
- Each bullet is user-meaningful, not implementation noise
- Breaking changes include migration action
- Security fixes are isolated in
Securitysection - Sections with no entries are omitted
- Duplicate bullets across sections are removed
Related Skills
Astrumon/code-decomposition
development
VerifiedTrustedCommunity
Enforces clean code decomposition following Uncle Bob's Clean Code principles and SOLID. Apply whenever writing functions, classes, or modules in any Kotlin/JVM project.
SKILL.mdUpdated Apr 18, 2026
Astrumon/architecture-designer
testing
VerifiedTrustedCommunity
Use this skill when designing new system architecture, reviewing existing designs, evaluating technology trade-offs, or making architectural decisions. Triggers on "architecture", "design decision", "ADR", "trade-off", "module structure", or system-level design questions.
SKILL.mdUpdated Apr 16, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026