vLLM Ascend Release Note Writer

Generate structured vLLM Ascend release notes from commits between two tags.

3|17|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/intellistream/vllm-ascend-hust --skill vllm-ascend-release-note-writer-intellistream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vLLM Ascend Release Note Writer
Source: https://github.com/intellistream/vllm-ascend-hust/tree/main/.agents/skills/vllm-ascend-release-note-writer
Command: npx skills add https://github.com/intellistream/vllm-ascend-hust --skill vllm-ascend-release-note-writer-intellistream

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv, requests, and includes scripts (resource) components.

What problem does it solve?

This skill automates the creation of release notes for vLLM Ascend by analyzing commits between tags and organizing changes into structured sections for publication.

Core Features & Use Cases

  • Generate release notes by fetching commits, categorizing changes into Highlights, Features, Performance, Dependencies, and Other sections, and outputting to the release note directory.
  • Support end-to-end workflows from commit collection to draft and final notes, including handling complex histories such as diverged branches and cherry-picks across releases.
  • Provide a guided workflow aligned with the project's references and tooling, enabling consistent, publish-ready notes for each release.

Quick Start

Run the release-note writer by providing base and head tags to generate notes in vllm-ascend-release-note/output/$version.

Frequently Asked Questions about vLLM Ascend Release Note Writer

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

FAQPage Schema
How do I automate release notes generation from commits between two tags?

To automate release notes generation, this skill analyzes commits between provided base and head tags, categorizing changes into Highlights, Features, Performance, Dependencies, and Other sections for structured output.

How are cherry-picks and diverged branches handled when generating a changelog?

Generating a changelog for complex histories like diverged branches and cherry-picks is handled by fetching commits and organizing changes into structured sections, ensuring consistent publish-ready notes across releases.

Do I need python-dotenv and requests to generate vLLM Ascend release notes?

Yes, you need python-dotenv and requests installed in your environment to run the scripts that fetch commits and output the final vLLM Ascend release notes to the designated directory.

What is the best way to categorize commit changes into Highlights and Features sections?

The best way to categorize commit changes into Highlights and Features sections is using an automated workflow that analyzes commit histories between tags and structures them into predefined publication categories.

Can I output draft and final release notes for vLLM Ascend end-to-end?

Yes, you can output draft and final release notes for vLLM Ascend end-to-end by running the guided workflow, which outputs the structured notes to the vllm-ascend-release-note/output/$version directory.