skills.rest
kagenti
kagentiOFFICIAL
Explore all skills by this author →
GitHub

github:prs

Analyze open GitHub Pull Requests for stale PRs, merge conflicts, and failing CI checks.

292|103|Updated Mar 27, 2025
Search Tags:#automation#code review#pull request#github#maintenance#ci
One-click install
npx skills add https://github.com/kagenti/kagenti --skill github-prs-kagenti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github:prs
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/github%3Aprs
Command: npx skills add https://github.com/kagenti/kagenti --skill github-prs-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage and maintain the health of GitHub Pull Requests by identifying those that need attention, are blocked by CI, or are becoming stale.

Core Features & Use Cases

  • Identify PRs Ready for Review: Find PRs with passing CI but no review.
  • Detect Stale PRs: Surface PRs that haven't been updated in over 14 days.
  • Flag Failing CI: Highlight PRs with broken checks.
  • Detect Merge Conflicts: Identify PRs that cannot be merged directly.
  • Use Case: Use this Skill during weekly code grooming to quickly identify PRs that are blocked, stale, or ready for immediate review, ensuring a smoother development workflow.

Quick Start

Analyze open pull requests on the kagenti/kagenti repository to identify stale PRs.

Frequently Asked Questions about github:prs

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

FAQPage Schema
How do I find stale GitHub pull requests in my repository?▼

To find stale GitHub pull requests, this skill analyzes open PR metadata via GitHub CLI and flags those untouched for over 14 days, helping maintainers prioritize code grooming.

What is the best way to identify pull requests with failing CI checks?▼

Identifying pull requests with failing CI checks is done by querying GitHub PR status, allowing you to highlight broken checks and focus developer attention on blocked branches.

How do I detect merge conflicts across open GitHub PRs?▼

You can detect merge conflicts across open GitHub PRs by analyzing PR mergeable states with GitHub CLI, flagging branches that cannot be merged directly for immediate developer action.

Can I use GitHub CLI to find PRs that are ready for review?▼

Yes, you can use GitHub CLI to find PRs ready for review by filtering for those with passing CI checks but no assigned reviewers, streamlining your code review workflow.

Do I need GitHub CLI installed to automate pull request maintenance?▼

Yes, you need GitHub CLI installed because this skill utilizes GitHub CLI commands to query PR status and metadata, enabling automated detection of stale PRs and failing CI checks.

Related Skills

Explore More Software Engineering Skills→
hammadparveezhammadparveez

github

Automate GitHub repository operations using the gh CLI.

Community
Intermediate
WaterplanAIWaterplanAI
31

cpc

Copy text to the macOS clipboard using the pbcopy utility.

Official
Basic
ilonatommyilonatommy
3

ci-analysis

Analyze Azure DevOps and Helix CI build and test failures for .NET pull requests.

Community
Advanced
Agents2AgentsAIAgents2AgentsAI
92

babysit-pr

Monitor GitHub pull requests by polling CI status, workflow runs, and mergeability until merge or close.

Official
Advanced