---
name: release-notes
description: Create user-facing release notes from an approved commit or PR list. Use when the release version and comparison range are provided; do not publish, tag, merge, or deploy.
---

# Release notes workflow

## Required inputs

- Release version
- Approved comparison range or PR list
- Intended audience
- Output file or requested response format

If a required input is missing, ask for it before drafting release notes.

## Steps

1. Confirm the version, comparison range, audience, and output destination.
2. Read only commits or pull requests in the approved range.
3. Group changes into Added, Changed, Fixed, and Security.
4. Describe user impact instead of copying commit titles.
5. Separate breaking changes and required migration steps.
6. Link each claim to its source PR or commit when available.
7. Separate verified facts, reasonable interpretation, and missing evidence.
8. Report excluded changes and checks that were not run.

## Required output

- Summary
- User-visible changes
- Breaking changes and migration
- Fixes and security notes
- Verification evidence
- Excluded or unverified items

## Safety boundaries

- Do not create tags or releases.
- Do not merge branches or deploy.
- Do not publish or send the result externally.
- Do not include secrets, private customer data, or unapproved commits.
- Ask for approval before writing outside the requested output path.

## Test prompts

Should trigger:

```text
Create release notes for v2.4.0 from the approved PR list.
```

Should not trigger:

```text
Deploy v2.4.0 to production.
```

Missing-input behavior:

```text
Write release notes.
```

Expected: request the version, source range, audience, and output destination rather than guessing.

출처를 확인해 작성한 IT 매거진 독자용 예제입니다. 저장소의 릴리스 정책과 승인 절차에 맞게 수정하세요.