vLLM Ascend Release Note Writer

Generate vLLM Ascend release notes from commits between two tags.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Release note generation between vLLM Ascend versions is manual and error-prone; this skill automates the extraction of commits between two tags and produces structured notes for release documentation.

Core Features & Use Cases

  • Automates tag-to-commit resolution and commit retrieval from GitHub.
  • Analyzes commits to draft highlights and PR-level summaries, organized into a publish-ready notes structure.
  • Supports diverged-release scenarios and output organization under vllm-ascend-release-note/output/$version.

Quick Start

Trigger the release notes generation for a new vLLM Ascend version by providing the base and head tags.

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 GitHub commits between two tags?

Release notes generation between two tags is automated by harvesting commits via the GitHub API, analyzing them through CSV drafts, and drafting highlights into a structured output directory. You provide base and head tags to trigger the extraction workflow.

What is the best way to resolve tag SHAs and fetch commits for release documentation?

Resolving tag SHAs and fetching commits is handled automatically by querying the GitHub API. The process retrieves commit history between your specified base and head tags to build the foundational data for release documentation.

Do I need the gh CLI to generate vLLM Ascend release notes?

The gh CLI is not strictly required but is used for generate-notes when available. Core functionality relies on a Python environment with requests and dotenv to interact with the GitHub API and manage environment variables.

How does commit analysis work for diverged release scenarios?

Commit analysis for diverged releases works by comparing base and head tags, fetching intermediate commits, and organizing them into CSV drafts. This supports drafting PR-level summaries and highlights for complex release workflows.

Where are the finalized release notes output stored?

Finalized release notes are stored under vllm-ascend-release-note/output/$version. This directory structure organizes the generated highlights and summaries into a publish-ready format for the specified release version.