skills.rest
flyonspeed
flyonspeedOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-notes

Aggregates PRs between tags into formatted OnSpeed Gen3 firmware release notes with recalibration callout.

Updated Aug 27, 2026
Search Tags:#documentation#github#calibration#firmware#release-notes#pr-review
One-click install
npx skills add https://github.com/flyonspeed/OnSpeed-Gen3 --skill release-notes-flyonspeed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/flyonspeed/OnSpeed-Gen3/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/flyonspeed/OnSpeed-Gen3 --skill release-notes-flyonspeed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The release-notes skill helps engineering teams produce consistent, high-quality GitHub release notes for OnSpeed-Gen3 firmware by summarizing changes, including the mandatory recalibration callout, and preventing accidental publication.

Core Features & Use Cases

  • Automates drafting of release notes for a new firmware version by aggregating PRs between the previous tag and the target, summarizing changes, and formatting them into a standard template.
  • Enforces the recalibration requirement whenever changes affect calibration data, ensuring pilots are informed of needed steps.
  • Produces a draft release notes file at /tmp/v<version>-release-notes.md that can be reviewed and published by the user.

Quick Start

Draft a GitHub release notes draft for the next OnSpeed-Gen3 firmware version, summarizing changes since the previous tag and including the recalibration note.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate firmware release notes from merged GitHub PRs?▼

To generate firmware release notes, aggregate merged GitHub PRs between the previous tag and the target version, summarize their diffs, and format the output into a standard release-note template saved as a markdown file.

How do I include recalibration warnings in firmware release notes?▼

Include recalibration warnings in firmware release notes by detecting calibration data changes within the PR diffs, which triggers a mandatory recalibration callout block to be injected into the standard release-note template.

Can I automatically draft non-marketing GitHub release notes?▼

Yes, you can automatically draft non-marketing GitHub release notes by aggregating PR bodies and diffs, ensuring the generated summaries remain strictly technical and free of promotional language before outputting the markdown file.

Does generating release notes automatically publish the GitHub tag?▼

No, generating release notes does not publish or create the GitHub tag. The process strictly produces a draft markdown file at a temporary path to preserve safety, requiring manual review before any publication.

What is the best way to summarize GitHub PR diffs for release documentation?▼

The best way to summarize GitHub PR diffs for release documentation is to aggregate changes between tags, analyze the code diffs and PR bodies, and format the technical summaries into a structured markdown template.

Do I need access to PR diffs to draft firmware release notes?▼

Yes, you need access to PR diffs and bodies to draft firmware release notes, as summarizing these changes is required to accurately populate the structured template and determine if recalibration is needed.

Related Skills

Explore More Content & Communication Skills→
saw4405saw4405

create-github-release

Create a GitHub Release from a semantic version input with diffs and a Windows ZIP artifact.

Community
Advanced
christianhellechristianhelle
413

release-process

Automates secure release publishing with SemVer checks, GitHub tagging, and npm rollback safeguards.

Community
Advanced
forgivesam168forgivesam168
2

git-commit

Analyze diffs and stage changes to generate conventional git commit messages.

Community
Basic
perminder-klairperminder-klair
1.2k

subwave-release-pr

Create a develop-to-main release pull request with a conventional-commit grouped summary.

Community
Advanced