midnite-triage

Generates a read-only markdown summary table of open GitHub pull requests and issues.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-triage-bilo-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: midnite-triage
Source: https://github.com/bilo-io/midnite-studio/tree/main/.agents/skills/midnite-triage
Command: npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-triage-bilo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scanning dozens of open pull requests and issues one by one in GitHub is slow, and it is hard to see at a glance which PRs are ready to land, which are failing checks, and which are stale. This Skill produces a single scannable triage table without changing anything in the repository. ## Core Features & Use Cases - One-table PR triage: Lists open PRs with clickable links and emoji marks for checks, review decision, mergeability, author kind (bot/human/draft), and age, sorted most-actionable-first. - Optional issues section: Adds a second table of open issues with labels, assignees, and age when invoked with issues or all. - Read-only guarantee: Never runs review, merge, comment, label, push, or any write operation — it only reports. - Use Case: Before standup, run the triage to get a footer like 12 open · 3 ready to land · 2 failing plus a one-sentence recommendation for the highest-value next action. ## Quick Start Ask the assistant to run the midnite-triage skill for all open PRs in the current repository and show the summary table.

Frequently Asked Questions about midnite-triage

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

FAQPage Schema
How do I get a quick summary of all open pull requests on GitHub?▼

Run this triage skill, which uses a single batched gh pr list query with JSON fields for checks, review decision, mergeable state, and labels. It renders one markdown table with clickable PR links and emoji status marks, sorted so ready-to-land PRs appear first.

How to triage GitHub PRs with the gh CLI?▼

Use gh pr list --state open --json with fields like statusCheckRollup, reviewDecision, and mergeable, then roll each field up into one status per PR. This skill automates that query and formats the results as a scannable table with a counts footer.

Does this skill modify or merge any pull requests?▼

No, the skill is strictly read-only. It never runs gh pr review, merge, comment, close, edit, label, or any git write operation; it only reports the state of each PR and may suggest a next action without taking it.

Can I triage issues as well as pull requests?▼

Yes, pass issues or all as the argument to add an Issues table with labels, assignees, and age under its own heading. The default scope is prs only, and --repo owner/name overrides the target repository.

How are failing checks and review states shown in the report?▼

Each column uses one emoji mark: checks show pass, failing, pending, or none; review shows approved, changes requested, review required, or none; merge shows mergeable, conflicting, or unknown. A legend line in the footer explains the marks used.