How do I install the Changelog Release Notes skill?

Run npx skillmds@latest add nowledge-co/changelog-release-notes 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 Changelog Release Notes 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 Changelog Release Notes?

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 Changelog Release Notes free to use?

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

Who published Changelog Release Notes?

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

Changelog Release Notes by nowledge-co

Name: Changelog Release Notes
Author: nowledge-co

File contents

Changelog Release Notes

Use this skill whenever CHANGELOG.md, PR release notes, or release summaries are touched.

Workflow

Verify the latest released beta before choosing a heading:
- git fetch --tags origin
- git tag --sort=-v:refname | rg '^v[0-9]+\\.[0-9]+\\.[0-9]+-beta\\.' | head
- gh release view <tag> when GitHub release state matters
Put pending work under the next unreleased beta only. If the latest shipped beta is v0.1.0-beta.63, the top unreleased heading is v0.1.0-beta.64; do not create beta.65 until beta.64 is tagged and released.
Gather PR and author context for every entry:
- gh pr view <number> --json number,title,author,url,mergedAt
- for merged work, git log <latest-tag>..HEAD --merges --oneline helps find the included PRs
Every PR-derived changelog bullet must end with PR and author credit:
- _(PR [#149](https://github.com/nowledge-co/con-terminal/pull/149) by [@sundy-li](https://github.com/sundy-li))_
Credit contributors exactly by GitHub login. Preserve external contributor credit even when follow-up commits refine the same feature.
Keep shipped historical sections stable. Only edit old sections to correct a factual mistake, missing credit, or broken link.

Writing Rules

Write for users first: describe the visible behavior or benefit, not the internal implementation unless it explains a risk or platform boundary.
Use Added, Changed, and Fixed sections. Group bullets under concise audience/platform labels such as macOS, Windows, Linux, Panes, or Developer Experience.
Do not mention "workspace restore" or other baseline continuity as novelty unless the user-facing behavior truly changed. Default expected behavior should read as polish or reliability, not marketing.
Add release dates only when a version is actually tagged/released.
If a bullet combines multiple PRs, include all relevant PR/author credits.

Validation

Confirm the heading matches the latest shipped beta plus one.
Confirm every new PR-derived bullet has PR [#...] and by [@...].
Run python3 scripts/docs/validate-manifest.py when docs routing may be affected.
Run git diff --check before committing.

---name: changelog-release-notesdescription: Maintain Con's CHANGELOG.md and release notes. Use when updating changelog entries, preparing a beta/dev release, reviewing PR release-note coverage, or ensuring contributor PR credit is present.---# Changelog Release NotesUse this skill whenever `CHANGELOG.md`, PR release notes, or release summariesare touched.## Workflow1. Verify the latest released beta before choosing a heading: - `git fetch --tags origin` - `git tag --sort=-v:refname | rg '^v[0-9]+\\.[0-9]+\\.[0-9]+-beta\\.' | head` - `gh release view <tag>` when GitHub release state matters2. Put pending work under the next unreleased beta only. If the latest shipped beta is `v0.1.0-beta.63`, the top unreleased heading is `v0.1.0-beta.64`; do not create `beta.65` until `beta.64` is tagged and released.3. Gather PR and author context for every entry: - `gh pr view <number> --json number,title,author,url,mergedAt` - for merged work, `git log <latest-tag>..HEAD --merges --oneline` helps find the included PRs4. Every PR-derived changelog bullet must end with PR and author credit: - `_(PR [#149](https://github.com/nowledge-co/con-terminal/pull/149) by [@sundy-li](https://github.com/sundy-li))_`5. Credit contributors exactly by GitHub login. Preserve external contributor credit even when follow-up commits refine the same feature.6. Keep shipped historical sections stable. Only edit old sections to correct a factual mistake, missing credit, or broken link.## Writing Rules- Write for users first: describe the visible behavior or benefit, not the internal implementation unless it explains a risk or platform boundary.- Use `Added`, `Changed`, and `Fixed` sections. Group bullets under concise audience/platform labels such as `macOS`, `Windows, Linux`, `Panes`, or `Developer Experience`.- Do not mention "workspace restore" or other baseline continuity as novelty unless the user-facing behavior truly changed. Default expected behavior should read as polish or reliability, not marketing.- Add release dates only when a version is actually tagged/released.- If a bullet combines multiple PRs, include all relevant PR/author credits.## Validation- Confirm the heading matches the latest shipped beta plus one.- Confirm every new PR-derived bullet has `PR [#...]` and `by [@...]`.- Run `python3 scripts/docs/validate-manifest.py` when docs routing may be affected.- Run `git diff --check` before committing.

Frequently asked questions

Changelog Release Notes

File contents

Changelog Release Notes

Workflow

Writing Rules

Validation

Related skills

Frequently asked questions

How do I install the Changelog Release Notes skill?

What does the Changelog Release Notes skill do?

Is Changelog Release Notes safe to use?

Which AI agents work with Changelog Release Notes?

Is Changelog Release Notes free to use?

Who published Changelog Release Notes?