medcore-pr-triage

Classify GitHub pull requests into close, comment, rebase, or merge actions.

2|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-pr-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medcore-pr-triage
Source: https://github.com/Globussoft-Technologies/medcore/tree/main/.claude/skills/medcore-pr-triage
Command: npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-pr-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time and risk required to triage a backlog of open PRs by deterministically classifying each PR (mergeable vs conflict vs checks status) and recommending the safest next action.

Core Features & Use Cases

  • PR mergeability × check-state triage: Classifies each open PR into close, comment, rebase, or merge based on mergeable and mergeStateStatus plus statusCheckRollup.
  • Failure-cluster diagnosis for UNSTABLE checks: Distinguishes real PR bugs from stale CI/rebase-needed issues and infra flakes, then chooses drill-down vs rebase vs re-dispatch guidance.
  • Operational guardrails for contributor workflows: Detects first-time-contributor cases where GitHub Actions require the “Approve and run workflows” human step, and directs the maintainer appropriately.

Use Case Example: When there are 3+ open human-authored PRs, it helps you quickly determine which ones can be squashed/merged green, which ones need comments to unblock fixes (e.g., contract/test mismatches), and which ones require rebasing or workflow approval instead of risky force operations.

Quick Start

Tell the AI: “Check the open human PRs and triage them (close/comment/rebase/merge) based on mergeability and CI state, skipping dependabot PRs.”

Frequently Asked Questions about medcore-pr-triage

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

FAQPage Schema
How do I triage multiple open GitHub pull requests based on mergeability and CI check state?

To triage open pull requests, classify each PR into close, comment, rebase, or merge actions by evaluating the mergeability and statusCheckRollup fields via GitHub CLI. This produces an ordered, safety-first execution plan for your backlog.

How do I diagnose failing CI checks to distinguish real bugs from stale CI or infra flakes?

Diagnose failing UNSTABLE checks by performing failure-cluster analysis to bucket failures into real-bug, stale-CI, or infra-flake categories. This determines whether to drill down, rebase, or re-dispatch the workflow.

What is the best way to handle first-time-contributor pull requests blocked by GitHub Actions?

Handle blocked first-time-contributor pull requests by detecting workflow runs that require the “Approve and run workflows” human step. Direct the maintainer to provide workflow approval instead of attempting risky force operations.

Can I automatically squash merge pull requests that are behind the main branch?

You can squash merge pull requests classified as safe by the mergeability matrix. PRs that are behind or have conflicts are directed to rebase first, ensuring superseded PRs are closed without risky force operations.

When should I close a superseded pull request during backlog cleanup?

Close a superseded pull request during backlog cleanup when failure-cluster analysis or mergeability checks show it is entirely blocked or redundant. This prevents risky merges and streamlines the queue for actionable PRs.

Does pull request triage work with dependabot automated PRs?

Pull request triage targets human-authored PRs and skips dependabot PRs. It focuses on classifying mergeable states and diagnosing UNSTABLE failing checks for human contributions requiring maintainer review.