release-notes-writer
/release-notes-writer
Tworzy gotowe do wysłania notatki wydania ze specyfikacji i zgłoszeń, zarówno dla użytkowników, jak i wewnętrzne dla inżynierów.
- Autor
- qa-aman ↗
- Repozytorium
- claude-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 19.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 19.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy gotowe do wysłania notatki wydania ze specyfikacji i zgłoszeń, zarówno dla użytkowników, jak i wewnętrzne dla inżynierów.
Oryginalny opis (EN)
Generate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets
Jak działa
- Workflow
- User-Facing Release Notes
- Internal Release Notes
- Writing Guidelines
- Anti-Patterns
- Quality Checklist
Podgląd SKILL.md
---
name: release-notes-writer
description: |
Generate ship-ready release notes from specs and tickets. Use this skill when:
- A release is being prepared and you need user-facing release notes
- You need internal (engineering) release notes for a deployment
- You want to generate release notes from completed specs or tickets
---
# Release Notes Writer
Generate structured release notes for each release cycle. Produces both **user-facing** (what changed and why it matters) and **internal** (technical changes, migration steps) release notes.
## Workflow
1. **Identify release scope** — List the features/fixes included
2. **Read source specs** — Read relevant spec files
3. **Read tickets** — If available, read completed tickets for the release
4. **Categorize changes** — Group into: New Features, Enhancements, Bug Fixes, Known Issues
5. **Write user-facing notes** — What changed, why it matters, in plain language
6. **Write internal notes** — Technical changes, migration steps, config changes
7. **Output** — Write to file
## User-Facing Release Notes
```markdown
# [Product Name] — Release Notes {version}
**Release Date:** {DD-MM-YYYY}
**Environment:** {Production / Staging / UAT}
## What's New
### {Feature Name}
{1-2 sentence description of what the feature does and why it matters.}
**Highlights:**
- {Key capability 1}
- {Key capability 2}
## Enhancements
### {Enhancement Name}
{What improved and why it's better now.}
| Before | After |
|--------|-------|
| {Old behavior} | {New behavior} |
## Bug Fixes
| Issue | Fix | Impact |
|-------|-----|--------|
| {description} | {what was fixed} | {who is affected} |
## Known Issues
| Issue | Workaround | Expected Fix |
|-------|-----------|-------------|
| {description} | {workaround} | {target version} |
```
## Internal Release Notes
```markdown
# Internal Release Notes — {version}
**Release Date:** {DD-MM-YYYY}
**Release Manager:** [your name]
**Deployment Type:** {Rolling / Blue-Green / Canary}
## Changes by Service
| Ticket | Type | Summary | Breaking? |
|--------|------|---------|-----------|
| {KEY-123} | Feature | {Summary} | No |
## Configuration Changes
| Config Key | Old Value | New Value | Service | Notes |
|-----------|-----------|-----------|---------|-------|
## Database Migrations
| Migration | Description | Reversible? | Duration |
|-----------|-------------|-------------|----------|
## Rollback Plan
{Steps to rollback if critical issues found}
## Monitoring Checklist
| Metric | Expected | Alert Threshold | Dashboard |
|--------|----------|-----------------|-----------|
```
## Writing Guidelines
### User-Facing
1. **Lead with benefits, not features** — "You can now track X" not "Added X API"
2. **Use plain language** — No technical jargon
3. **Be specific** — "Reports now show time per topic" not "Improved reports"
4. **Acknowledge bug fixes honestly**
### Internal
1. **Be precise** — Include ticket numbers, endpoint paths, config keys
2. **Flag breaking changes prominently**
3. **Include rollback steps**
4. **Reference monitoring dashboards**
## Anti-Patterns
- Don't write "various improvements" — be specific
- Don't skip the rollback plan for internal notes
- Don't use technical jargon in user-facing notes
- Don't forget known issues — transparency builds trust
## Quality Checklist
- [ ] User-facing notes use plain language
- [ ] Every change categorized (feature/enhancement/bug fix)
- [ ] Internal notes include ticket numbers
- [ ] Rollback plan documented
- [ ] Breaking changes flagged
- [ ] Known issues listed
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · qa-aman/claude-skills | 100 | MIT |
| JayRHa/AgentSkills | 100 | MIT |
| ArabelaTso/Skills-4-SE | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki c82dcabd36bd (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90release-notes
Tworzy informacje o wydaniu dla użytkowników końcowych z commitów od ostatniego tagu, bez żargonu deweloperskiego. - 100create-release-notes
Generuje notatki wydania dla użytkowników: dokumentuje release, streszcza zmiany i przygotowuje changelog między wersjami. - 100release-notes
Tworzy ze zgłoszeń, PRD-ów lub changelogów zrozumiałe notatki wydania, pogrupowane na nowości, usprawnienia i poprawki. - 100release-notes
Zamienia listę wdrożonych zmian w notatki wydania dla różnych odbiorców: changelog dla użytkowników, wewnętrzny log co, dlaczego i wpływ oraz krótkie ogłoszenie do social mediów. - 100release-notes
Zbiera PR-y i commity przez gh CLI, kategoryzuje zmiany i tworzy sformatowane notatki między tagami wydania. - 100release-notes
Generuje notatki Markdown do najnowszego wydania repozytorium GitHub na podstawie podanego adresu owner/repo lub URL.