agentleFS
product-on-purposeproduct-on-purpose/pm-skills/skills/utility-pm-changelog-curator/SKILL.md

utility-pm-changelog-curator

Skill777 starsChanged 10 months agoApache-2.0View on GitHub

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.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the canonical sub-agent definition at agents/pm-changelog-curator.md

    line 43
  2. Distinctive:

    Run the 8-step drafting flow documented in the sub-agent definition (establish range -> read hygiene rules -> check working tree -> …

    line 45
  3. Distinctive:

    Read CLAUDE.md hygiene rules and existing CHANGELOG.md format reference

    line 54
  4. Distinctive:

    Read the canonical sub-agent definition file

    line 55
  5. Distinctive:

    Treat the agent body as operating instructions

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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:

  1. Read the canonical sub-agent definition at agents/pm-changelog-curator.md
  2. Execute the system prompt body in that file as your operating instructions
  3. 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)
  4. Apply --since-tag, --target-version, and --committed-only arguments from $ARGUMENTS
  5. 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:

  1. Execute Bash for git log, git describe, and git status invocations
  2. Read CLAUDE.md hygiene rules and existing CHANGELOG.md format reference
  3. Read the canonical sub-agent definition file
  4. 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: site/src/content/docs/reference/runtime-components.md
  • Output template: references/TEMPLATE.md
  • Worked example: references/EXAMPLE.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.