semver-changelog
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.
More from prulloac/agent-skills
github-pull-request
Create pull requests on GitHub using GitHub MCP, GitHub CLI (gh), or the GitHub REST API. Use this skill when the user wants to submit changes as a pull request, following repository standards and templates.
20custom-agent-creator
Skill to create custom agents for VS Code Copilot or OpenCode, helping users configure and generate agent files with proper formatting and configurations. Use when users want to create specialized AI assistants for VS Code Copilot (.agent.md files) or OpenCode (JSON/markdown agent configs) with specific tools, prompts, models, and behaviors. If the user is not specific about the target platform, ask them to specify Copilot or OpenCode.
20markdown-crossref-validator
Validate cross-references in markdown documents, ensuring links and references point to existing sections, headings, or files.
14vscode-extension-builder
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.
14system-prompt-validator
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.
13github-pr-comments
Analyze and manage GitHub pull request comments with automated categorization, severity assessment, and intelligent response handling. Use when working with PR comments to understand feedback patterns, prioritize issues, or automatically address reviewer concerns. Leverages GitHub MCP Server, GitHub CLI (gh), or GitHub REST API in order of precedence.
12