write-release-notes

Draft tldraw SDK release notes from GitHub releases with structured frontmatter.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/seflless/tldraw-agent-claude-code-provider --skill write-release-notes-seflless
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-release-notes
Source: https://github.com/seflless/tldraw-agent-claude-code-provider/tree/main/.claude/skills/write-release-notes
Command: npx skills add https://github.com/seflless/tldraw-agent-claude-code-provider --skill write-release-notes-seflless

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting consistent and comprehensive release notes for tldraw SDK releases, ensuring clarity, attribution, and alignment with the project's documentation style.

Core Features & Use Cases

  • Structured guidance on assembling release notes from GitHub releases, including identifying sections like API changes, bug fixes, and improvements.
  • Style-compliant templates that ensure consistent voice, tone, and formatting across all release articles.
  • Contributor crediting and link integration to GitHub releases for traceability and attribution.

Quick Start

Draft a release notes article by aggregating changes from the target GitHub release and formatting it to the apps/docs/content/releases template.

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 GitHub releases?

Automate release notes generation by aggregating changes from a target GitHub release and formatting them into a structured article with frontmatter, categorization, and attribution links.

What is the best way to format SDK release notes for a style guide?

Format SDK release notes by aligning content with a project style guide, applying structured frontmatter, and categorizing API changes, bug fixes, and improvements into a standardized article template.

How do I structure API changes and bug fixes in release notes?

Structure API changes and bug fixes in release notes by categorizing them into distinct sections, applying standardized frontmatter with versioning data, and integrating GitHub links for contributor attribution.

Can I draft release notes for tldraw SDK releases without manual formatting?

Draft tldraw SDK release notes without manual formatting by consolidating GitHub release data into a style-compliant template that automatically handles voice, tone, and contributor crediting.

Does this approach work for consolidating GitHub releases into documentation?

Consolidating GitHub releases into documentation works by extracting changes from the release source and mapping them directly into the project's apps/docs/content/releases template format.

Why do my release notes lack consistent contributor crediting and traceability?

Release notes lack consistent contributor crediting when link integration to GitHub releases is omitted; standardizing attribution within the article template resolves traceability gaps.