sdk-changelog

Generate structured changelogs for SDK packages from PR data and commit history.

395|94|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/tetherto/qvac --skill sdk-changelog-tetherto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdk-changelog
Source: https://github.com/tetherto/qvac/tree/main/.cursor/skills/sdk-changelog
Command: npx skills add https://github.com/tetherto/qvac --skill sdk-changelog-tetherto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive and human-readable changelogs for SDK packages, simplifying release documentation and communication.

Core Features & Use Cases

  • Automated Changelog Creation: Generates detailed changelogs and release notes for SDK pod packages following a structured format.
  • PR Filtering & Categorization: Excludes irrelevant PRs and categorizes changes into sections like features, bug fixes, and models to enhance clarity.
  • Use Case: When preparing for a new SDK release, use this Skill to produce polished changelogs, summaries, and Slack announcement posts automatically.

Quick Start

Use the sdk-changelog skill to generate a human-readable changelog for the latest SDK release, saving it as CHANGELOG_LLM.md for review and publication.

Frequently Asked Questions about sdk-changelog

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

FAQPage Schema
How do I automate SDK changelog creation from git commit history and PR data?

Automating changelog creation involves parsing PR data and commit history to generate structured release notes. The process filters irrelevant PRs and categorizes changes into features, bug fixes, and models, producing a formatted markdown file for SDK release documentation.

What is the best way to generate structured release notes for a monorepo SDK?

Generating structured release notes for a monorepo SDK requires parsing PR data and version tags to categorize updates. This approach excludes irrelevant PRs and groups changes into clear sections, ensuring accurate communication of features and bug fixes across packages.

Can I filter and categorize pull requests automatically when generating SDK release notes?

Yes, filtering and categorizing pull requests during release note generation is supported. The mechanism excludes irrelevant PRs and sorts changes into specific categories like features and bug fixes to enhance documentation clarity.

Do I need Node and Git installed to automate changelog generation for SDK packages?

Yes, Node and Git are required dependencies to automate changelog generation. The environment uses Git to access commit history and PR data, while Node executes the scripts needed to process and format the release documentation.

How do I format Slack announcement posts for a new SDK release?

Formatting Slack announcement posts for an SDK release involves summarizing categorized PR data and commit history. The process generates polished summaries and release notes from version tags, creating ready-to-publish communication content for Slack.