mcpbeat Sign in

Utility Pm Changelog Curator Agent Skill

Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when banking unreleased changes or preparing a release.

5k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
516
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/product-on-purpose/pm-skills --skill utility-pm-changelog-curator

The instruction itself

8 sections, as written by the author

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

PM Changelog Curator (Dispatch Skill)

Cross-client dispatch wrapper for the pm-changelog-curator sub-agent. Detects runtime; dispatches to the native sub-agent on Claude Code; reads agents/pm-changelog-curator.md and executes inline on non-Claude clients.

When to Use

  • You are preparing a release and want a CHANGELOG draft from git log between two tags
  • You are running on a non-Claude AI client without native pm-changelog-curator sub-agent support
  • You want a draft that respects pm-skills CHANGELOG hygiene rules (no internal-notes references, no em-dashes, public paths only) without manually applying them

When NOT to Use

  • You want to commit CHANGELOG entries directly (this skill produces a draft for review, not a commit)
  • You want to review a PM artifact -> use utility-pm-critic instead
  • You want a repo-wide governance audit -> use utility-pm-skill-auditor
  • You want a full guided release flow -> use utility-pm-release-conductor (which chains to this skill at gate G2)

Instructions

Runtime detection step. Determine which AI client is invoking this skill.

If you are running in Claude Code with the pm-skills plugin installed

Invoke @agent-pm-skills:pm-changelog-curator with the user's arguments. Pass --since-tag, --target-version, --committed-only from $ARGUMENTS if present. Return the sub-agent's draft to the user.

If you are running in any other AI client

Codex CLI, Cursor, Windsurf, Copilot, Gemini CLI, or any other client without native pm-skills plugin sub-agent support:

  • Read the canonical sub-agent definition at agents/pm-changelog-curator.md
  • Execute the system prompt body in that file as your operating instructions
  • Run the 8-step drafting flow documented in the sub-agent definition (establish range -> read hygiene rules -> check working tree -> enumerate commits -> classify -> group -> rewrite -> determine target version -> emit draft)
  • Apply --since-tag, --target-version, and --committed-only arguments from $ARGUMENTS
  • Return the layered output per master plan D26 (full CHANGELOG draft + Status Summary + Status YAML)

Cross-Client Notes

The dispatch skill requires the AI client to:

  • Execute Bash for git log, git describe, and git status invocations
  • Read CLAUDE.md hygiene rules and existing CHANGELOG.md format reference
  • Read the canonical sub-agent definition file
  • Treat the agent body as operating instructions

See Sub-Agent Compatibility Matrix for the canonical cross-client status. Summary for this skill as of v2.16.0: PRODUCTION on Claude Code + Codex CLI (Codex CLI successfully ran git log + read CLAUDE.md hygiene rules + drafted clean CHANGELOG entries + correct dirty-tree refusal); EXPERIMENTAL on Cursor / Windsurf / Copilot CLI / Gemini CLI. If a client is unreliable, fall back to manual git log + manual drafting using CLAUDE.md as the hygiene reference.

Reference Files

  • Canonical sub-agent definition: agents/pm-changelog-curator.md
  • Behavioral spec: docs/internal/release-plans/v2.16.0/spec_pm-changelog-curator.md
  • CHANGELOG hygiene rules source: CLAUDE.md (repo root)
  • Existing CHANGELOG.md format: CHANGELOG.md (root); v2.15.1 + v2.15.2 entries are canonical exemplars
  • Runtime components catalog: docs/reference/runtime-components.md
  • Output template: references/TEMPLATE.md
  • Worked example: references/EXAMPLE.md

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take product-on-purpose/utility-pm-changelog-curator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.