skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

write-release-notes

Generate formatted markdown release notes from merged pull requests for dotnet/extensions.

3.2k|886|Updated Feb 17, 2015
Search Tags:#GitHub#release notes#version tracking#markdown generation#pull request analysis
One-click install
npx skills add https://github.com/dotnet/extensions --skill write-release-notes-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-release-notes
Source: https://github.com/dotnet/extensions/tree/main/.github/skills/write-release-notes
Command: npx skills add https://github.com/dotnet/extensions --skill write-release-notes-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github/*, sql, ask_user, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of drafting release notes for the dotnet/extensions repository, significantly reducing the manual effort required to document changes and updates.

Core Features & Use Cases

  • Automated PR Analysis: Gathers and analyzes merged pull requests, categorizing them by area and impact.
  • Experimental API Tracking: Identifies and documents changes to experimental APIs.
  • Version Information: Determines package versions for release notes.
  • Release Notes Drafting: Composes formatted markdown release notes.
  • User Confirmation: Ensures user review and approval before release.

Quick Start

Use the write-release-notes skill to generate release notes for the latest release of dotnet/extensions.

Frequently Asked Questions about write-release-notes

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

FAQPage Schema
How do I automate release notes generation from merged pull requests?▼

You can automate release notes generation by analyzing merged pull requests, categorizing changes by area and impact, tracking experimental APIs, and composing formatted markdown. This skill requires GitHub API access and SQL for data storage.

What is the best way to track experimental API changes for version releases?▼

The best way to track experimental API changes is by analyzing merged pull requests to identify modifications, documenting them, and determining package versions to compose formatted markdown release notes.

Do I need GitHub API access to generate markdown release notes for dotnet extensions?▼

Yes, GitHub API access is required to generate markdown release notes for dotnet extensions. The process analyzes merged pull requests, tracks experimental APIs, and relies on SQL for data storage and PR analysis tools.

How does pull request analysis work for categorizing release notes?▼

Pull request analysis for categorizing release notes works by gathering merged PRs, categorizing them by area and impact, tracking experimental APIs, determining package versions, and drafting formatted markdown release notes for user review.

Can I review and approve release notes before they are published?▼

Yes, you can review and approve release notes before publication. The generation process includes a user confirmation step to ensure user review and approval of the formatted markdown release notes before the final release.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
3.2k

update-otel-genai-conventions

Analyze OpenTelemetry GenAI semantic-conventions changes and plan compensating updates for dotnet/extensions.

Official
Advanced
uhyouhyo
88

release-funstack

Automate version bumps, commits, and GitHub releases with generated notes.

Community
Advanced
chenxingqiangchenxingqiang

changelog-scan

Extract titles, labels, and types from merged pull requests and commits via GitHub APIs.

Community
Basic
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

git-release

Draft release notes from merged pull requests and propose version bumps.

Community
Intermediate