Use when writing concise, copy-ready Markdown release notes from changelog entries and commits.
php artisan boost:add-skill alizharb/agent-skills
Save this content to: .claude/skills/write-release-notes/SKILL.md
# Write Release Notes
## Workflow
1. Inspect the changelog, commits since the previous tag, and notable docs changes.
2. Group notes into Added, Improved, Fixed, Changed, and Validation.
3. Explain user-facing value before implementation details.
4. Mention breaking changes and migration steps clearly.
5. Keep notes copy-ready for GitHub Releases.
## Verification
- Version matches the tag.
- Notes do not claim unverified CI success.
## Common Mistakes
- Listing internal file changes without explaining user value.
How can I help you explore Laravel packages today?