skills.rest
mangowhoiscloud
mangowhoiscloudCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

geode-changelog

Manage GEODE changelogs following Keep a Changelog and SemVer standards.

13|2|Updated Feb 21, 2026
Search Tags:#changelog#release management#versioning#documentation#semver#keep a changelog
One-click install
npx skills add https://github.com/mangowhoiscloud/geode --skill geode-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: geode-changelog
Source: https://github.com/mangowhoiscloud/geode/tree/main/.claude/skills/geode-changelog
Command: npx skills add https://github.com/mangowhoiscloud/geode --skill geode-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the process of documenting changes for the GEODE project, ensuring clear, consistent, and comprehensive release notes.

Core Features & Use Cases

  • Changelog Management: Adheres to Keep a Changelog and SemVer standards for versioning and formatting.
  • Scope Definition: Clearly defines what should and should not be included in changelogs.
  • Workflow Integration: Provides a step-by-step process for updating changelogs during development and before releases.
  • Use Case: When a new feature is added to GEODE, this Skill guides the developer on how to correctly document it in the CHANGELOG.md file, ensuring it's ready for the next release.

Quick Start

Follow the GEODE changelog convention to document recent changes.

Frequently Asked Questions about geode-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a changelog using Keep a Changelog and SemVer standards?▼

To manage a changelog with Keep a Changelog and SemVer, you document new features, bug fixes, and architectural changes under specific version headers. This ensures clear, consistent release notes by enforcing standardized formatting and scope definition for project releases.

What is the best way to document architectural changes in a CHANGELOG.md file?▼

Documenting architectural changes in a CHANGELOG.md file requires categorizing them under standardized sections like added or changed. Following Keep a Changelog conventions ensures these structural modifications are clearly communicated and consistently formatted for release notes.

How do I generate changelog entries from Git commit history?▼

Generating changelog entries from Git commit history involves integrating your workflow with commit logs to track changes efficiently. This process streamlines changelog generation by guiding developers to document recent updates correctly within versioned release sections.

What should not be included when writing release notes for software versioning?▼

When writing release notes for software versioning, trivial internal updates or non-user-facing changes should not be included. Defining a clear scope prevents cluttering the changelog, ensuring only meaningful features, bug fixes, and architectural changes are documented.

How do I update a changelog during development before a release?▼

To update a changelog during development, add new entries to an Unreleased section at the top of the file as you implement features or fixes. This step-by-step workflow integration keeps your release notes ready for the next versioning cycle.

Related Skills

Explore More Software Engineering Skills→
pantheon-orgpantheon-org
9

conventional-commits

Generate Git commit messages following the Conventional Commits specification.

Official
Intermediate
KewtonKewton

release-post

Convert CHANGELOG.md release notes into social media post content.

Community
Intermediate
duongdevduongdev
9

commit-assistant

Generate conventional commit messages from git changes and link them to Linear issues.

Community
Intermediate
gaebalaigaebalai
2

release-tag-plan

Plan release tagging and CHANGELOG strategy using semantic versioning.

Community
Advanced