How do I install the Release Note Writer skill?

Run npx skillmds@latest add tomevault-io/release-note-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Note Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Note Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Note Writer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Note Writer?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Note Writer by tomevault-io

Name: Release Note Writer
Author: tomevault-io

Release Note Writer

Generate and update release notes for sanhe-claude-code-plugins. Use when user wants to create or update release notes, document version changes, or prepare for a new release. Reads git commit history, pyproject.toml version, and follows the standardized format. Use when this capability is needed.

tomevault-io b224bee 2 files · 3.2 KB Updated Sep 17, 2026

File contents

Release Note

Generate and update release notes following the standardized format for this repository.

Workflow

Step 1: Gather Information

Read references/format-standard.md to understand the release note format
Get current version from pyproject.toml using: grep "^version" pyproject.toml
Get the last release tag: git tag -l | tail -1 (if no tags, this is the initial release)
Get commit history since last tag:
- If tag exists: git log <last-tag>..HEAD --oneline
- If no tag: git log --oneline

Step 2: Analyze Changes

Review each commit message to identify changes
Map changes to the format: {plugin_name}@{category}@{feature_name}
Categorize each change as: Add, Update, Fix, or Remove
Cross-reference with plugins/ directory structure to verify accuracy

Step 3: Handle Conflicts

If information from user conflicts with what you read:

Ask user to confirm the correct information
User input takes precedence after confirmation

Step 4: Update release-history.rst

Read current release-history.rst
Update the version entry with:
- Correct version number from pyproject.toml
- Today's date in YYYY-MM-DD format
- Entries grouped by change type (Add, Update, Fix, Remove)
- Alphabetical order within each group
Omit empty change type sections

Entry Format

- {plugin_name}@{category}@{feature_name}: {brief description}

Valid Categories

skills - Agent skills
slash-commands - Slash commands
agents - Custom subagents
hooks - Automation hooks

Change Types

Add - New additions
Update - Modifications to existing features
Fix - Bug fixes
Remove - Deletions

Example Output

0.1.1 (2025-01-13)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

**Add**

- mini-kanban@skills@mini-kanban: file-based task management
- mini-kanban@slash-commands@mini-kanban: kanban command wrapper
- youtube@skills@youtube-video-to-audio: YouTube to audio converter

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: release-note-writerdescription: Generate and update release notes for sanhe-claude-code-plugins. Use when user wants to create or update release notes, document version changes, or prepare for a new release. Reads git commit history, pyproject.toml version, and follows the standardized format. Use when this capability is needed.---# Release NoteGenerate and update release notes following the standardized format for this repository.## Workflow### Step 1: Gather Information1. Read `references/format-standard.md` to understand the release note format2. Get current version from `pyproject.toml` using: `grep "^version" pyproject.toml`3. Get the last release tag: `git tag -l | tail -1` (if no tags, this is the initial release)4. Get commit history since last tag: - If tag exists: `git log <last-tag>..HEAD --oneline` - If no tag: `git log --oneline`### Step 2: Analyze Changes1. Review each commit message to identify changes2. Map changes to the format: `{plugin_name}@{category}@{feature_name}`3. Categorize each change as: Add, Update, Fix, or Remove4. Cross-reference with `plugins/` directory structure to verify accuracy### Step 3: Handle ConflictsIf information from user conflicts with what you read:- Ask user to confirm the correct information- User input takes precedence after confirmation### Step 4: Update release-history.rst1. Read current `release-history.rst`2. Update the version entry with: - Correct version number from pyproject.toml - Today's date in YYYY-MM-DD format - Entries grouped by change type (Add, Update, Fix, Remove) - Alphabetical order within each group3. Omit empty change type sections## Entry Format```- {plugin_name}@{category}@{feature_name}: {brief description}```### Valid Categories- `skills` - Agent skills- `slash-commands` - Slash commands- `agents` - Custom subagents- `hooks` - Automation hooks### Change Types- **Add** - New additions- **Update** - Modifications to existing features- **Fix** - Bug fixes- **Remove** - Deletions## Example Output```rst0.1.1 (2025-01-13)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~**Add**- mini-kanban@skills@mini-kanban: file-based task management- mini-kanban@slash-commands@mini-kanban: kanban command wrapper- youtube@skills@youtube-video-to-audio: YouTube to audio converter```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/machu-gwu) — claim your Tome and manage your conversions.

Frequently asked questions