release-notes Skill
Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release. Published by microsoft in haste.
Decision snapshot
Is this a fit?
Documentation, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is release-notes Skill?
Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release. Published by microsoft in haste. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Writing
- Documentation use cases
- Writing use cases
Declared skill metadata
- Source file: .github/skills/release-notes/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use release-notes Skill
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/haste
- Skill file: .github/skills/release-notes/SKILL.md
What it does
Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release.
Skill instructions
Release Notes Overview A structured process for generating release notes from commit history. Groups changes by type, highlights breaking changes, and produces user-friendly summaries. Patterns & Techniques Generation Process Step 1: Gather changes bash git log --oneline $(git describe --tags --abbrev=0)..HEAD Step 2: Categorize using conventional commit prefixes: - 🚀 Features (feat:) - 🐛 Bug Fixes (fix:) - 📚 Documentation (docs:) - 🔧 Maintenance (chore:, refactor:) - ⚠️ Breaking Changes (BREAKING CHANGE or !) Step 3: Write using the template: markdown Release vX.Y.Z Highlights Brief summary of the most important changes (2-3 sentences). 🚀 Features - Description of feature (PR) 🐛 Bug Fixes - Description of fix (PR) ⚠️ Breaking Changes - What changed and migration steps 📚 Documentation - What was updated 🔧 Maintenance - Internal changes Step 4: Review - All significant changes included - PR/issue references correct - Breaking changes include migration instructions Common Pitfall
Verified compatibility and discovery
Frequently asked questions
What is release-notes?
release-notes is a open-source AI agent skill with Copy skill directory. Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release.
Who is release-notes best for?
release-notes is best for reusing agent instructions, scripts, and references, documentation workflows, writing workflows.
How do I install release-notes?
Install or run release-notes using Copy skill directory. Check release-notes for the latest setup command.
Is release-notes actively maintained?
release-notes may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
