Stats
Actions
Tags
From sde-execution
Developer-facing changelog from commit list or PR titles: categorized sections (feat/fix/breaking/deprecated/security). Use when generating a changelog for a release.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sde-execution:release-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Good release notes tell users what changed and why it matters. They're not a git log dump — they're a curated, human-readable summary of significant changes.
Good release notes tell users what changed and why it matters. They're not a git log dump — they're a curated, human-readable summary of significant changes.
Commits, PRs, or version changes to document: $ARGUMENTS
Classify every change into one of these categories (following Conventional Commits):
feat: New feature or capability
fix: Bug fix — describe the bug, not just the fix
security: Security fix — always document these clearly
perf: Performance improvement with measurable numbers
breaking: BREAKING CHANGE — this changes existing behavior
deprecated: Feature being phased out (include migration path)
docs: Documentation update (usually skip in user-facing notes)
chore: Internal tooling, deps update (often skip unless security)
## [Version] — [Release Date]
### Breaking Changes
> **Action required before upgrading:** [instructions]
- **[Component]:** [What changed and what you need to do] — ([PR #N](link))
- Before: `old behavior`
- After: `new behavior`
- Migration: [step-by-step migration instructions]
---
### New Features
- **[Feature name]:** [What it does and why it's useful] — ([PR #N](link))
```javascript
// Example usage
Recommend upgrading immediately.
[new feature] instead: [example][Only include if relevant to developers: tooling changes, dependency upgrades with impact]
[Any specific steps required to upgrade, database migrations, configuration changes]
---
### Rules for Good Release Notes
Write from the user's perspective, not the engineer's Bad: "Refactored UserRepository to use repository pattern" Good: "Fixed intermittent login failures under high load"
Include numbers for performance changes Bad: "Improved search performance" Good: "Search API now returns results in 50ms (down from 400ms on large catalogs)"
Breaking changes must include migration instructions Bad: "Renamed getUser to findUser" Good: "Renamed getUser to findUser — update all callsites: s/getUser/findUser/g"
Security fixes: vague but honest Don't expose the attack vector (helps attackers who haven't upgraded) Do tell users to upgrade immediately "Fixed authentication bypass in /api/admin routes — recommend immediate upgrade"
Don't document internal changes unless they affect users/developers CI improvements, linting changes, internal refactors: skip
Link to migration guides for complex changes "See migration guide for step-by-step upgrade instructions"
---
### From Raw Commits
If given a list of commits:
8a7b3d1 fix login bug a3c92f0 add rate limiting bc71234 update deps d1e9031 perf: faster search queries e2f4567 BREAKING: rename getUser to findUser f3g5678 add 2FA support
getUser to findUser — update all usagesProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub chavangorakh1999/sde-skills --plugin sde-execution