release-notes
Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release.
소스 정보
- 저장소
- microsoft/haste
- 최근 소스 활동
- 2026년 6월 17일 22:19
- 감지된 SKILL.md 언어
- 영어
- 스타
- 109
- 포크
- 19
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- release-notes
- description
- Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release.
- source
- Internal engineering practices
- domain
- documentation
- level
- foundational
- agents
- ["orchestrator","backend-dev"]
- created_date
- 2026-04-27
- last_validated
- validated_by
- status
- draft
# 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 Pitfalls
- **Listing commit messages verbatim** — Rewrite for the reader, not the committer
- **Missing breaking changes** — Always call these out prominently with migration steps
- **No highlights section** — Users want a 2-sentence summary, not a raw list
GitHub에서 보기