report-next-release

Generate a two-tab HTML report of what is queued for the next Fedi release.

78|27|Updated May 4, 2024
One-click install
npx skills add https://github.com/fedixyz/fedi --skill report-next-release-fedixyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-next-release
Source: https://github.com/fedixyz/fedi/tree/main/.agents/skills/report-next-release
Command: npx skills add https://github.com/fedixyz/fedi --skill report-next-release-fedixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Release status in the Fedi repo is scattered across git branches, web tags, GitHub milestones, PR bodies, and Zenhub boards, so answering "what is going into the next release" requires hours of manual cross-referencing that is easy to get wrong. ## Core Features & Use Cases - Window resolution: Derives native and web release baselines, lists every PR merged to master since, and resolves each referenced issue with its milestone, labels, and Zenhub board state via a bundled resolver script. - Two-altitude HTML report: Renders a self-contained dark-mode page with a plain-language Summary tab for non-technical readers and a Full report tab with PR-by-PR detail, QA sign-off, and backport state. - Milestone hygiene: Buckets issues as done, in progress, pending, or backport, and prepares milestone-tagging commands that are only run after explicit user approval. - Use Case: A product manager asks what is shipping in Fedi 26.7; the skill pins both release tracks, resolves the merge window, and produces a report plus a chat briefing in one pass. ## Quick Start Ask the assistant to report what is going into the next Fedi release, including milestone status and QA sign-off.

Frequently Asked Questions about report-next-release

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

FAQPage Schema
How do I report what is going into the next Fedi release?

Run the skill against the fedibtc/fedi repo: it pins the native release branch and newest web tag as baselines, resolves every PR merged since, and renders a self-contained HTML report with a Summary tab and a Full report tab.

How does the report decide whether milestone work is done?

Status comes from repo evidence, not issue state: a merged window PR means done, an open non-draft PR means in progress, and a draft or no PR means planned. Zenhub board columns are used to catch missing PR links, never to override git.

Does the skill support both the native app and the web app?

Yes, it tracks two independent release lines: native ships from a release/26.M branch while web ships as web/X.Y.Z tags deployed through a manual Vercel workflow. Each track gets its own baseline, window, and lane in the report.

What tools does the release report need to run?

It needs git with the repo checked out, the GitHub CLI (gh) for PRs, milestones and issues, and optionally the Zenhub CLI for Dev Team and QA board state. Without a Zenhub key it warns and marks board state unavailable.

Will the skill tag milestones or move board issues automatically?

No. It prepares the gh issue edit commands for untagged resolved issues and prints them with a review link, but runs nothing until the user explicitly approves. It never moves issues on the shared Zenhub boards.