skills.rest
bilo-io
bilo-ioCOMMUNITY
Explore all skills by this author →
GitHub

midnite-retro

Generates read-only retrospectives of merged GitHub work grouped into themes over a chosen window.

Updated Sep 1, 2026
Search Tags:#github#retrospective#pull requests#gh cli#report#read-only#engineering summary
One-click install
npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-retro-bilo-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: midnite-retro
Source: https://github.com/bilo-io/midnite-studio/tree/main/.agents/skills/midnite-retro
Command: npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-retro-bilo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers "what actually shipped" across a GitHub org, user, or repo over a given period without manually digging through hundreds of merged PRs, releases, and commits. ## Core Features & Use Cases - Scoped gathering: Confirms scope, focus categories, time window (1m/3m/6m/1y), and author filter before scanning, then fans out read-only subagents over active repos. - Themed classification: Groups merged PRs into themes by epic references, conventional-commit scopes, labels, and paths, tagging categories like Features, Maintenance, Fixes, and evidence-based Innovation. - Use Case: Ask for a retro on your org for the last 3 months focused on innovation and features, and receive a markdown report of grouped PRs plus a summary explaining why each novel item mattered. ## Quick Start Run a retro on my-org for the last 3 months focused on innovation and features.

Frequently Asked Questions about midnite-retro

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

FAQPage Schema
How do I generate a retrospective of merged PRs on GitHub?▼

Invoke the skill with an owner or owner/repo and a window like 1m, 3m, 6m, or 1y. It confirms scope, focus categories, and author filter, then scans merged PRs and releases with the gh CLI and returns a themed markdown report.

What GitHub CLI permissions are needed for an org retro?▼

The gh CLI must be authenticated, and listing org repos requires the read:org scope, while private org repos also need the repo scope. If user/orgs returns empty, refresh the token with gh auth refresh -s read:org.

Does the retro skill modify repositories or issues?▼

No, it is strictly read-only. It performs no PR or issue writes, comments, labels, pushes, or file edits; the only optional write is a shareable HTML report page in the scratchpad if the user requests it.

How does the skill decide which work counts as innovation?▼

A PR is marked novel only with concrete evidence, such as being first of its kind in the org, introducing a new technology, replacing a known approach, showing measured improvements, enabling later work, or being explicitly exploratory.

What happens with repos that push directly to the default branch?▼

When a repo has no merged PRs but recent pushes, the skill falls back to listing commits since the start date via the GitHub API and treats each commit subject like a PR title for classification.

Related Skills

Explore More Software Engineering Skills→
forcedotcomforcedotcom
803

switching-org

Switch the Salesforce CLI target-org configuration for subsequent commands.

Official
Basic
shekerkammashekerkamma

presentation-exporter

Export HTML presentations to PDF, PNG, and markdown speaker notes.

Community
Intermediate
s0613s0613
1

sj-retro

Aggregate git, test, and friction data into structured engineering retro reports.

Community
Intermediate
zero-rehqzero-rehq

release-notes

Generate CHANGELOG.md and GitHub release notes from commits and worklog data.

Community
Advanced