Release Notes

Community

Mehdibargach

release-notes

Turn git commits, tickets, or raw notes into user-facing release notes. Adjustable tone (B2B formal, B2C friendly, internal).

Overview

Publisher	Mehdibargach
Repository	`claude-code-pm-skills`
Skill name	`release-notes`
Stars	97
Forks	38
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Mehdibargach on GitHub. Read the source before you install it.

Installation

Install the Release Notes AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Mehdibargach/claude-code-pm-skills/tree/main/skills/release-notes
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Mehdibargach/claude-code-pm-skills.git /tmp/claude-code-pm-skills
mkdir -p .claude/skills
cp -r /tmp/claude-code-pm-skills/skills/release-notes .claude/skills/release-notes

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Release Notes in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Release Notes on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Release Notes is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Release Notes Generator

Transform raw engineering artifacts (git commits, Jira tickets, changelogs, raw notes) into polished, user-facing release notes. Write for users, not engineers.

Process

Read the input — either from a provided file path or from pasted commits/tickets in the argument.
If a git repository path is provided, use git log --oneline (read-only) to extract recent commits.
Group changes into categories: New features, Improvements, Bug fixes.
Translate each technical change into user-facing language.
Infer the tone from context. If not clear, default to B2B Formal.
Write the release notes.
Save the output to a file in the current working directory as release-notes-[version-or-date].md.

Output Format

[Release Title — descriptive, not just a version number]

Version: [if applicable] Date: [release date]

New Features

For each feature:

[Feature name] — What it does and why it matters to the user. Not how it was built.

Improvements

For each improvement:

[What improved] — What the user will notice is better. Be specific.

Bug Fixes

For each fix:

[What was fixed] — Describe the problem the user experienced, not the technical root cause.

Internal Notes (optional, only if requested)

Technical details relevant for support teams, CSMs, or internal stakeholders
Migration notes, feature flags, rollout percentages
Known issues that weren't fixed in this release

Tone Guide

B2B Formal:

Professional, clear, concise
"We've introduced..." / "This release includes..."
Suitable for enterprise customers, changelog pages

B2C Friendly:

Warm, conversational, benefit-focused
"You can now..." / "We fixed a bug that..."
Suitable for consumer apps, in-app changelogs

Internal:

Direct, technical context included
Can reference ticket numbers, feature flags, team names
Suitable for Slack updates, internal wikis

Rules

Write for USERS, not engineers. Translate every change into user impact.
"Fixed null pointer exception in auth service" becomes "Fixed an issue where some users couldn't log in."
"Refactored payment module" becomes an Improvement only if users notice something — otherwise omit it.
Internal refactors with zero user impact should be omitted from user-facing notes (move to Internal Notes if needed).
Group related commits into a single release note item. Five commits about the same feature = one bullet point.
Never expose internal system names, error codes, or infrastructure details in user-facing sections.
If the tone is not specified, default to B2B Formal.
Every item must answer: "Why should the user care?"

Frequently asked questions

What does the Release Notes AI skill do?

Turn git commits, tickets, or raw notes into user-facing release notes. Adjustable tone (B2B formal, B2C friendly, internal).

Why use Release Notes on TypingMind?

Because you install it once and use it with any model. Release Notes is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Release Notes in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Mehdibargach/claude-code-pm-skills/tree/main/skills/release-notes. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Release Notes?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Release Notes?

As many as you like. As long as a model supports skills, you can use Release Notes with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Release Notes AI skill free?

It is published on GitHub by Mehdibargach. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Release Notes Generator

Process

Output Format

[Release Title — descriptive, not just a version number]

New Features

Improvements

Bug Fixes

Internal Notes (optional, only if requested)

Tone Guide

Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now