oscar-changelog-maintenance

Maintain date-based CHANGELOG.md entries with Keep a Changelog categories.

Updated Sep 6, 2025
One-click install
npx skills add https://github.com/kabaka/oscar-export-analyzer --skill oscar-changelog-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oscar-changelog-maintenance
Source: https://github.com/kabaka/oscar-export-analyzer/tree/main/.github/skills/oscar-changelog-maintenance
Command: npx skills add https://github.com/kabaka/oscar-export-analyzer --skill oscar-changelog-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains CHANGELOG.md following Keep a Changelog format with date-based versioning, ensuring that user-facing and contributor-facing changes trigger timely documentation.

Core Features & Use Cases

  • Enforces a dated section for each release (e.g., 2026-02-07) and standard categories like Added, Changed, Fixed, Security.
  • Guides when to add entries for new features, UI/UX improvements, bug fixes, and documentation updates.
  • Provides a repeatable workflow for auditors and maintainers to verify changelog coverage during releases.

Quick Start

Add today's date section to CHANGELOG.md and document user-facing changes under the appropriate categories.

Frequently Asked Questions about oscar-changelog-maintenance

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

FAQPage Schema
How do I maintain a CHANGELOG.md with date-based versioning?

To maintain a CHANGELOG.md with date-based versioning, add a dated section for each release and document user-facing changes under standard categories like Added, Changed, Fixed, and Security.

What is the best way to format release notes for software versioning?

Formatting release notes for software versioning requires standard categories such as Added, Changed, Fixed, and Security, ensuring per-entry formatting maintains consistent documentation for features, fixes, and updates.

When should I add entries to a changelog during release management?

You should add entries to a changelog when new features, UI/UX improvements, bug fixes, or documentation updates occur, ensuring timely documentation of user-facing and contributor-facing changes for each release.

How do I verify changelog coverage before a software release?

Verify changelog coverage before a software release by applying a repeatable workflow for auditors and maintainers to check that all version entries and date sections follow the required formatting.

Does this changelog workflow follow the Keep a Changelog format?

Yes, this changelog workflow follows the Keep a Changelog format, enforcing dated sections for releases and standard categories to document user-facing and contributor-facing changes consistently.

Can I use this approach to document contributor-facing changes?

Yes, you can use this approach to document contributor-facing changes alongside user-facing changes, applying consistent entries for each version to ensure complete release notes and documentation coverage.