prulloac/semver-changelog
.agents/skills/semver-changelog/SKILL.md
Automate the creation and updating of a CHANGELOG.md file based on Semantic Versioning (SemVer) and "Keep a Changelog" principles. Use this skill when you need to summarize changes between the current HEAD and the latest git tag, or when initializing a new changelog for a project.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add prulloac/git-blame-vsc semver-changelogInstall 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 24, 2026, 8:49 PM1.8s1 file scanned
SKILL.md
- name:
- semver-changelog
- description:
- Automate the creation and updating of a CHANGELOG.md file based on Semantic Versioning (SemVer) and "Keep a Changelog" principles. Use this skill when you need to summarize changes between the current HEAD and the latest git tag, or when initializing a new changelog for a project.
Semver Changelog
This skill guides the agent through identifying released versions, analyzing git history, and documenting changes in a standard format.
Overview
A consistent changelog helps users and contributors understand what has changed between versions. This skill ensures that CHANGELOG.md follows the Keep a Changelog format and adheres to Semantic Versioning.
Workflow
Follow these steps to update or create the changelog:
1. Identify Latest Released Tag
Find the most recent git tag that follows Semantic Versioning (e.g., v1.2.3 or 1.2.3).
- Use
git tag -l --sort=-v:refnameto list tags in version order. - Filter for tags that match the
v?MAJOR.MINOR.PATCHpattern.
2. Analyze Changes
Compare the current HEAD with the identified latest tag to see what has changed.
- Run
git diff <latest_tag>..HEADto see code changes. - Run
git log <latest_tag>..HEAD --onelineto see commit messages.
3. Group and Categorize Changes
Group the identified changes into the following categories:
- Added: New features.
- Changed: Changes in existing functionality.
- Deprecated: Soon-to-be removed features.
- Removed: Now removed features.
- Fixed: Bug fixes.
- Security: Security vulnerability fixes.
4. Update CHANGELOG.md
Update the CHANGELOG.md file at the repository root.
- If it doesn't exist, create it using the standard header.
- Add an
[Unreleased]section if it doesn't exist, or update the existing one with the new changes. - Ensure the file follows the "Keep a Changelog" structure.
Guidelines
- Refer to references/semver_reference.md for detailed formatting and versioning rules.
- Always check the repository root for an existing
CHANGELOG.mdbefore creating a new one. - Use the
[Unreleased]section for changes that haven't been tagged yet.
Examples
Initializing a Changelog
If no changelog exists:
- Create
CHANGELOG.md. - Add the standard "Keep a Changelog" header.
- Identify all tags and their changes to build the history, or start from the latest tag.
Validation
After updating or creating the changelog, verify the following:
- File Existence: Ensure
CHANGELOG.mdexists at the repository root. - Format: Check that the file includes the required header and that new changes are correctly categorized under the appropriate heading (e.g.,
### Added). - Links: If the file uses links at the bottom for versions, ensure they point to valid git comparison URLs (if applicable).
- SemVer: Ensure the version numbers used follow the SemVer specification.
Example Output
When reporting the update to the user, you can use a format like this:
Changelog Update Summary
| Category | Changes Identified | | :--- | :--- | | Added | - New API endpoint for users | | Fixed | - Bug in authentication logic | | Security | - Updated dependencies to patch CVE-2023-XXXX |
Latest Version: [1.1.0] Previous Version: [1.0.0]
Related Skills
prulloac/vscode-extension-builder
tools
VerifiedTrustedCommunity
Guide for creating Visual Studio Code extensions/plugins. Use when users want to build VS Code extensions, add functionality to VS Code, create language support, add themes, build webviews, implement debuggers, or any VS Code plugin development task. Helps navigate VS Code Extension API documentation and provides guidance on extension capabilities, project setup, and best practices.
SKILL.mdUpdated Apr 16, 2026
prulloac/system-prompt-validator
development
VerifiedTrustedCommunity
Validate agent system prompts (such as agents.md) for being objective-driven, clear, readable, free of duplicated intentions, without missing or broken links, and ensuring required sections like general agentic guidelines, code review, and code generation are present. Use when validating or reviewing agent prompt files.
SKILL.mdUpdated Apr 16, 2026
prulloac/skill-validator
testing
VerifiedTrustedCommunity
Validate agent skills for correctness, readability, workflow clarity, and isolation, ensuring they can be installed independently without dependencies on other skills.
SKILL.mdUpdated Apr 16, 2026
prulloac/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
SKILL.mdUpdated Apr 16, 2026