skills.rest
cedanl
cedanlOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-notes

Draft Dutch release notes from merged PRs and closed issues.

Updated Nov 8, 2024
Search Tags:#automation#versioning#github#issues#pr#release-notes#dutch
One-click install
npx skills add https://github.com/cedanl/.github --skill release-notes-cedanl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/cedanl/.github/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/cedanl/.github --skill release-notes-cedanl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft Dutch release notes from merged PRs and closed issues since the last tag, then create a GitHub Release draft or final release when ready. This helps teams communicate changes to users without manual, repetitive writing.

Core Features & Use Cases

  • Automates gathering merged PRs and closed issues since the previous tag and converts them into structured release notes.
  • Classifies changes into categories (Nieuw, Opgelost, Verbeterd, Documentatie, Intern) to reflect user-visible impact.
  • Creates a GitHub Release draft for review and publishing, using the project's VERSION tag or a provided version.
  • Works as part of a release workflow to ensure timely, consistent, Dutch-language release notes for stakeholders.

Quick Start

Use the release-notes skill to generate Dutch release notes and create a GitHub Release draft for the next version.

Frequently Asked Questions about release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate generating Dutch release notes from merged PRs and closed issues?▼

Automating Dutch release notes involves gathering merged PRs and closed issues since the previous tag, classifying them into categories like Nieuw or Opgelost, and drafting a structured summary for end users. This requires access to repository data and uses the GitHub CLI.

What is the best way to create a GitHub Release draft from recent repository activity?▼

Creating a GitHub Release draft from recent activity involves pulling repository events since the last tag, structuring them into user-visible change categories, and pushing a draft release via the GitHub CLI. This ensures consistent, timely communication of project updates.

Do I need a VERSION file to draft release notes, or can I specify a version manually?▼

You do not strictly need a VERSION file to draft release notes. You can either specify a version manually when invoking the process or let the system derive the version automatically from the repository's VERSION file to create the GitHub Release draft.

How does categorizing merged PRs into Nieuw, Opgelost, and Verbeterd help end users?▼

Categorizing merged PRs into Nieuw, Opgelost, and Verbeterd translates technical repository activity into structured, user-visible impact categories. This helps end users quickly understand new features, bug fixes, and improvements without reading raw commit logs.

Does automating release notes work with standard GitHub issues and pull requests?▼

Yes, automating release notes works with standard GitHub issues and pull requests. The process requires access to repository data to fetch closed issues and merged PRs since the previous tag, using the GitHub CLI to assemble the notes.

Related Skills

Explore More Product & Management Skills→
TrainLCDTrainLCD
71

publish-release

Create git tags and GitHub Releases for the TrainLCD MobileApp repository.

Official
Intermediate
typemdtypemd
9

create-release

Gather closed issues and commits to draft release notes and create a GitHub draft release.

Official
Advanced
RepairYourTechRepairYourTech
6

github-actions

Create and manage CI/CD pipelines with GitHub Actions workflows.

Community
Advanced
dennisonbertramdennisonbertram
1

changelog-gen

Generate release notes from Git history using Conventional Commits and git-cliff.

Community
Advanced