Add dynamo-release-notes skill, trim dynamo-content-designer - #17298
Add dynamo-release-notes skill, trim dynamo-content-designer#17298jasonstratton wants to merge 1 commit into
Conversation
Split the release-notes curation-and-publish workflow out of dynamo-content-designer into its own skill: it's a multi-step process (curate, sweep, flag ambiguous calls, draft, cross-check against already-published content, validate, publish, verify) rather than a sentence-level writing task. dynamo-content-designer now redirects release-notes requests to the new skill instead of covering them itself.
There was a problem hiding this comment.
Pull request overview
This PR restructures Claude Code tooling in Dynamo by extracting the release-notes curation/publishing workflow out of dynamo-content-designer into a dedicated dynamo-release-notes skill, and updating repo guidance accordingly.
Changes:
- Added a new
dynamo-release-notesskill with supporting assets (curation rules, style guide, and wiki publishing plumbing). - Updated
dynamo-content-designerto remove embedded release-notes guidance and redirect release-notes requests to the new skill. - Updated
AGENTS.mdto reflect the new skill lineup and revised scope ofdynamo-content-designer.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| AGENTS.md | Updates the documented list of available skills and clarifies content-designer scope. |
| .claude/skills/dynamo-release-notes/SKILL.md | Introduces the new release-notes workflow skill and its end-to-end process. |
| .claude/skills/dynamo-release-notes/assets/curation-rules.md | Defines inclusion/dedup/security/breaking-change/credit/category rules for release notes curation. |
| .claude/skills/dynamo-release-notes/assets/style-guide.md | Provides sentence-level guidance for writing release-note bullets. |
| .claude/skills/dynamo-release-notes/assets/wiki-publish-plumbing.md | Documents a safe Windows-friendly git plumbing workflow for editing the wiki. |
| .claude/skills/dynamo-content-designer/SKILL.md | Removes release-notes responsibility and redirects to dynamo-release-notes. |
| .claude/skills/dynamo-content-designer/assets/release-notes.md | Removes the old embedded release-notes guidance (moved/replaced by the new skill’s assets). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| description: Curate, sweep, draft, cross-check, and publish the "### {version}" section | ||
| of the Dynamo GitHub wiki Release-Notes page, starting from the raw | ||
| ReleaseNotes_{X.Y.Z}.md generator dump. Use when compiling release notes for a Dynamo | ||
| release, deciding which PRs belong in a release's notes, or inserting/updating content | ||
| on the Release-Notes wiki page (https://github.com/DynamoDS/Dynamo/wiki/Release-Notes). |
| stage the entire wiki as deleted. Run `git status` immediately before creating the | ||
| commit and confirm it shows only the intended single-file change. **Ask the requester | ||
| to explicitly confirm before pushing** — a wiki push has no PR or review gate and is |
| ``` | ||
| git diff-tree <old-tree-sha> <new-tree-sha> | ||
| ``` |
|
|
||
| - User mentions writing documentation: "write a doc", "write an error message", "create a tutorial", "write up", "draft content" | ||
| - User mentions specific doc types: "blog post", "Primer article", "release notes", "feature documentation," "notification message" | ||
| - User mentions specific doc types: "blog post", "Primer article", "feature documentation," "notification message" |
|
edwin-vasquez-ucaldas
left a comment
There was a problem hiding this comment.
LGTM.
Only pending to address the copilot comments, I think just related with format/metadata/wrapper consistency issues and those comments make sense for me.



Purpose
Splits the release-notes curation-and-publish workflow out of the
dynamo-content-designerClaude Code skill into its own dedicated skill,dynamo-release-notes. Publishing a release's wiki notes turned out to be a multi-step process (curate the raw generator dump, run security/breaking-change/attribution/category sweeps, flag ambiguous calls for a human decision, draft prose, cross-check against everything already published to avoid duplicating an earlier patch release's notes, validate links/content, safely edit the wiki repo, verify post-publish) rather than a sentence-level writing task — worth its own skill rather than a subsection of a general content-writing skill.dynamo-content-designernow redirects release-notes requests to the new skill instead of covering them itself.This is Claude Code tooling only (
.claude/skills/,AGENTS.md) — no product code changes.Declarations
Release Notes
N/A
Reviewers
(none assigned yet)
FYIs
N/A