release-notes

Generate prover-facing release notes for Boundless versions from PRs and code changes.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Current-cmd/TrustMeBRO --skill release-notes-current-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/Current-cmd/TrustMeBRO/tree/main/.claude/skills/ops-release-notes
Command: npx skills add https://github.com/Current-cmd/TrustMeBRO --skill release-notes-current-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes for a new Boundless release requires digging through PRs, reading actual code changes, and translating them into documentation that prover operators can act on. This Skill automates that research and drafting process, producing accurate config examples, migration guides, and worked examples. ## Core Features & Use Cases - PR and Code Research: Fetches PR details via the GitHub CLI and reads the actual code (config structs, broker.toml template, compose.yml) so notes reflect real behavior, not just PR descriptions. - Operator-Focused Documentation: Produces sections covering what changed, how to enable it with TOML/CLI/env var examples, and an Upgrade Notes summary with action items. - Migration Guides & Worked Examples: Shows before/after config comparisons, flags breaking changes, and walks through realistic calculations using current market rates. - Use Case: When cutting Boundless v1.5.0, provide the previous tag and key PRs, and receive complete release notes with config snippets and upgrade instructions ready for prover operators. ## Quick Start Ask the assistant to generate release notes for Boundless version v1.5.0 compared against v1.4.0, highlighting the PRs you specify.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate release notes for a new Boundless version?▼

Provide the version number, the previous release tag to compare against, and the key PRs or features to highlight. The Skill fetches PR details with the GitHub CLI, reads the relevant code, and drafts prover-facing notes with config examples and upgrade steps.

What inputs are needed to write Boundless release notes?▼

You need the new version number, the previous release tag (e.g., v1.2.2), the key PRs or features to cover, and optionally current market context like USD/Bcycle pricing for realistic worked examples.

Does the release notes generator rely only on PR descriptions?▼

No. It reads the actual code, including config structs, default values, the broker.toml template, compose.yml, and the justfile, so config examples and CLI flags reflect real behavior rather than PR text alone.

Who is the intended audience for these release notes?▼

The audience is prover operators running the Boundless broker, not developers. The notes focus on config changes, CLI flags, operational impact, and migration steps rather than internal implementation details.

Can the release notes include migration guides for broker.toml changes?▼

Yes. The Skill produces before/after TOML comparisons, calls out removed, renamed, or re-defaulted fields, and notes backward compatibility so operators know whether existing configs still work.