What problem does it solve? Non-technical stakeholders cannot tell what a team is actually shipping from raw GitHub activity, because most pull requests and issues are internal engineering work. This Skill triages merged PRs, open PRs, and issues into a short, jargon-free report of what changed for users, what is in progress, and what is planned. ## Core Features & Use Cases - User-impact triage: Filters out tests, CI, refactors, and developer tooling, keeping only changes a person would notice in the product. - Verified release status: Uses the bundled shipped_status.py script to check whether merged work is contained in the actually deployed native and web builds, including cherry-picked releases and feature-flag gates, before calling anything Shipped. - Dual output rendering: Produces a self-contained HTML report and a matching inline markdown briefing from one JSON file via render_report.py, so both outputs never disagree. - Use Case: A founder asks "what did the team ship this month?" The Skill pulls recent GitHub activity, verifies liveness per platform, and returns a ranked ten-item briefing with links to the underlying work. ## Quick Start Ask the assistant to summarize what the team has shipped and is currently building in this repository as a plain-language product update.
