change-log-release-notes

Name: change-log-release-notes
Availability: InStock
Author: Tanveer

Maintains dated append-only change logs and generates release notes from them.

1|Updated Jun 3, 2026

Search Tags:#versioning #documentation #release notes #audit trail #change log #software release

Ready to run

npx skills add https://github.com/tanveerriaz/Skillz --skill change-log-release-notes-tanveerriaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-log-release-notes
Source: https://github.com/tanveerriaz/Skillz/tree/main/skills/change-log-release-notes
Command: npx skills add https://github.com/tanveerriaz/Skillz --skill change-log-release-notes-tanveerriaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changes made during development get forgotten between sessions, and release notes end up fabricated from memory. This Skill keeps a dated, append-only change log updated as work happens, then derives release notes strictly from those logs so nothing is invented or lost. ## Core Features & Use Cases - Daily Change Logging: Append timestamped entries to one log file per day, capturing the instruction, discovery, plan, files changed, and test results. - Release Notes Generation: Read only the relevant daily logs and produce user-readable notes grouped into Features, Improvements, Bug Fixes, Security, and Known Issues. - Use Case: After a week of feature work, ask for release notes for v0.9.3 and receive notes built from five daily logs, with each item rewritten in plain language and security changes called out explicitly. ## Quick Start Log this change to today's change log, then generate release notes for the upcoming version from the daily logs.

Frequently Asked Questions about change-log-release-notes

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

FAQPage Schema

How do I keep a change log during development?▼

Append a timestamped entry to a dated log file after each change, recording the instruction, discovery, plan, files changed, and test results. Use one file per day and keep the log append-only so prior entries are never overwritten.

How do I generate release notes from commit history or logs?▼

Read only the relevant daily log files for the release period, group changes into Features, Improvements, Bug Fixes, Security, and Known Issues, then rewrite each item in plain user-facing language. Never include items that do not appear in the logs.

What should a good change log entry include?▼

Each entry should contain a timestamp, the user instruction, searches run and what was found, the plan, files changed with one-line summaries, test results, and any risks or TODOs. Keep entries factual and concise.

What happens if there are no log entries for a release period?▼

State that there are no recorded changes for that period rather than guessing or inventing items. Release notes must derive solely from the logs, so missing logs mean no notes can be produced.

Should internal refactors appear in release notes?▼

Log internal refactors as usual, but in release notes summarize them as improvements without exposing internal details or file paths. Security and auth changes should always be called out explicitly in their own section.