← ClaudeAtlas

writing-release-noteslisted

Drafts DSPy release notes from maintainer-selected highlights and a verified, complete Git release range. Use when preparing or updating stable, beta, or release-candidate notes.
SOYL-AI/soyl-skills-hub · ★ 0 · AI & Automation · score 72
Install: claude install-skill SOYL-AI/soyl-skills-hub
# Writing DSPy Release Notes Ask what matters to the maintainer, then turn the complete release range into source-checked release notes in DSPy's established style. ## 1. Ask for highlights before drafting Start by asking: > Which PRs or features should headline this release? PR numbers, links, or feature names are fine. What version are we preparing, and is it stable, beta, or RC? Use information already supplied rather than asking again. If highlights are missing, **wait for the maintainer's answer before drafting**. If they ask you to choose, inspect the range and propose highlights yourself. Their choices determine emphasis, not which changes are included in the full list. Establish the previous release tag and target branch, tag, or commit. If unspecified, inspect releases and state a proposed baseline and target. Ask when multiple release lines make the scope ambiguous. Distinguish local `main` from `origin/main`; do not assume the checkout is current. If the release label is undecided, explain briefly: - Beta (`X.Y.Zb1`): APIs or behavior may still change based on testing and feedback. - RC (`X.Y.Zrc1`): intended final behavior; would ship unchanged if no blockers are found. - Both are prereleases. Do not describe either as stable. For a first beta, normally use the preceding stable release as the baseline. For subsequent betas, RCs, and the final release, establish whether the maintainer wants cumulative notes since stable or incremental n