skills.rest
mifunedev
mifunedevOFFICIAL
Explore all skills by this author →
Website𝕏@mifunedevGitHub

pr-audit

Audit open GitHub pull requests and classify them into triage buckets.

28|3|Updated Mar 27, 2026
Search Tags:#automation#github#triage#ci#pull-request#pr-audit#mergeability
One-click install
npx skills add https://github.com/mifunedev/openharness --skill pr-audit-mifunedev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-audit
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/pr-audit
Command: npx skills add https://github.com/mifunedev/openharness --skill pr-audit-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open PR queues can grow unmanageably large; this skill provides bulk PR auditing to surface actionable triage signals, reducing manual review burden and keeping progress transparent.

Core Features & Use Cases

  • Bulk fetch open PRs and classify into buckets: ready-to-merge, needs-review, CI-failing, conflicting/behind, and stale/convention flags.
  • Separate Drafts (promotable / WIP / limbo) for focused handling without polluting actionable buckets.
  • Optional mutation features (--deep, --proof, --label-apply, --close-stale) with explicit confirmation to guard changes.
  • Produce a structured triage report and persist a memory log for auditing.

Quick Start

Run a PR Audit against your repository to categorize and triage all open PRs with a single command.

Frequently Asked Questions about pr-audit

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

FAQPage Schema
How do I triage open pull requests in bulk on GitHub?▼

Bulk PR triage fetches open pull requests and classifies them into buckets like ready-to-merge, needs-review, CI-failing, and conflicting to reduce manual review burden. It reads PR metadata using GitHub CLI to categorize queues consistently.

What is the best way to categorize stale GitHub PRs and drafts?▼

Categorizing stale GitHub PRs separates drafts into promotable, WIP, or limbo buckets to keep actionable queues clean. It uses the updatedAt field to identify staleness and applies convention flags without polluting the ready-to-merge categories.

Does PR auditing check CI status and mergeability for open pull requests?▼

PR auditing checks CI status and mergeability by reading defined GitHub fields including status, reviewDecision, and mergeable state. This classification surfaces CI-failing and conflicting or behind PRs so reviewers can focus on actionable items.

Can I automatically close stale pull requests or apply labels during a PR audit?▼

You can automatically close stale pull requests or apply labels using optional mutation flags like --close-stale and --label-apply. These actions require explicit confirmation to guard against unintended changes to your repository.

How do I generate a structured triage report for multiple GitHub PRs?▼

Generating a structured triage report for multiple GitHub PRs produces categorized buckets and persists a memory log for auditing. It classifies pull requests by reviews, CI status, and mergeability to keep repository flow transparent and safe.

Related Skills

Explore More Software Engineering Skills→
x402agentx402agent

review-github-pr

Summarizes GitHub pull requests by distilling diffs and highlighting design decisions.

Community
Intermediate
amdmaxamdmax
2

finalize-story

Update GitHub issues, link pull requests, apply labels, and add stories to project boards.

Community
Advanced
OmniNode-aiOmniNode-ai
3

list-prs

Aggregate open pull request statuses from multiple GitHub repositories.

Official
Intermediate
mkittmkitt
6

copilot-review

Categorize Copilot pull request comments as Fix, Dismiss, or Decide.

Community
Intermediate