release-notes-curatelisted

Augments the open release-drafter draft on develop with project-context-aware sections per the canonical-language file under spec/project/release-skill-layer/ §"Skill A — Draft notes curation". Reads the project's audience artefact, derives a section bundle from the detected project type, wraps the augmentation in stable HTML-comment markers so re-runs update in place, and writes the body back via `gh release edit` for a release tag. Invoke when the user asks to "curate the release notes", "shape the release notes for this repo", or equivalent German-language requests. Don't use to publish the release (use `release-publish-trigger`), to identify audiences (use `audience-identify`), to draft notes from scratch (use the `audience-doc-author` agent), or to scaffold issue / PR templates (use `github-issue-templates-apply`). Supports resume on re-invocation per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · Data & Documents · score 76

Install: claude install-skill nolte/claude-shared

# Release Notes Curate Operationalises `spec/project/release-skill-layer/<canonical_language>.md` §"Skill A — Draft notes curation" against a target repository: classifies the project type, reads the audience artefact, derives a project-context section bundle, wraps it in stable markers below the `release-drafter` body, and writes back via `gh release edit --notes`. Idempotent on re-runs. ## Why this is a skill, not an agent - **Per-write user approval is the contract** — the spec mandates a disclose-and-confirm gate before any `gh release edit --notes`, because the body is externally visible on the GitHub release page; an agent's fire-and-forget shape would lose that gate. - **Output flows back into the main conversation** — the project-type classification, the section bundle preview, and the diff between existing and augmented body all surface in the conversation so the operator can correct the augmentation before commit. - **Orchestrator role** — when no audience artefact exists, this skill dispatches `audience-identify` first; the skill-orchestrates pattern (per `skill-vs-agent`) defaults the orchestrator to skill form. - Counter-dimension considered: a narrow Markdown-formatter agent could specialise on section composition, but the load-bearing dimension is the multi-step approval dialogue (project type → audience → bundle → diff → write), not the prose mechanics — skill wins. ## User-language policy Detect the user's language and respond in it. The release notes th