github-pr-triage_skill

This skill triages every open GitHub PR with real-time streaming analysis, assigns independent tasks, and surfaces actionable outcomes to accelerate
  • TypeScript

31.6k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill code-yeongyu/oh-my-opencode --skill github-pr-triage

  • SKILL.md15.3 KB

Overview

This skill triages GitHub pull requests using a streaming, agent-per-PR architecture. It fetches every open PR with exhaustive pagination, launches one independent background task per PR, and streams each analysis as it completes. The skill applies conservative auto-close logic and produces a final comprehensive report.

How this skill works

First, it collects all open PRs via exhaustive pagination. For each PR it launches exactly one background task that performs a focused analysis (comments, reviews, files changed, branch checks) and returns a strict, machine-parsable report. Results are streamed in real time as each task finishes; auto-close actions are conservative and require confirmation unless explicitly allowed. At the end it aggregates all analyses into a final comprehensive report.

When to use it

  • You need fast, parallel triage across many open PRs with live progress updates.
  • Maintainers want per-PR isolation so failures or slow analyses don’t block others.
  • You want conservative automated cleanup of clearly obsolete PRs with reviewable actions.
  • You need an auditable final report summarizing merge-ready, review-needed, stale, and closeable PRs.

Best practices

  • Always run exhaustive pagination to ensure no open PRs are missed.
  • Enforce 1 PR = 1 background task; never batch multiple PRs into one task.
  • Stream results immediately as each background task completes to surface urgent items early.
  • Use conservative auto-close criteria and require explicit confirmation before closing unless auto-close was pre-approved.
  • Rate-limit polling for background outputs to avoid excessive API / orchestration calls.

Example use cases

  • Nightly triage run that analyzes hundreds of open PRs in parallel and streams results to a dashboard.
  • On-demand cleanup: find and conservatively close PRs already implemented elsewhere or clearly abandoned.
  • Pre-release sweep to identify merge-ready PRs and surface blockers in real time.
  • Assign reviewers by streaming items that need human review while other analyses continue running.

FAQ

One task per PR ensures isolation, parallelism, resilience, and immediate streaming of each PR’s result. Batching PRs into a single task breaks these guarantees and is a blocking violation.

How does conservative auto-close work?

Auto-close is only recommended when the change is already implemented, merged elsewhere, explicitly deprecated, or the author is unresponsive for a long period. The skill asks for confirmation before executing closures unless auto-close permission is explicitly given.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
github-pr-triage skill by code-yeongyu/oh-my-opencode | VeilStrat