skills.rest
berkayturanci
berkayturanciCOMMUNITY
Explore all skills by this author →
Website𝕏@BerkayTuranciGitHub

keel-stale-prs

Identify, triage, and optionally rebase stale GitHub pull requests.

4|Updated May 23, 2026
Search Tags:#GitHub#rebase#triage#PR management#stale PRs
One-click install
npx skills add https://github.com/berkayturanci/keel --skill keel-stale-prs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keel-stale-prs
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-stale-prs
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-stale-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps streamline the process of identifying and managing stale open pull requests, reducing the manual effort required for triage and rebase operations.

Core Features & Use Cases

  • Stale PR Identification: Detects PRs that have gone quiet or drifted off the base branch.
  • Triage and Commenting: Automatically triages PRs and posts comments with suggestions for action.
  • Rebase Option: Optionally rebase non-draft PRs to bring them up to date with the base branch.
  • Dry Run Mode: Allows you to see what actions would be taken without making any changes.
  • Summary Report: Provides a summary of actions taken for each PR.

Quick Start

Run the command /keel:stale-prs to automatically check for and manage stale pull requests in your repository.

Frequently Asked Questions about keel-stale-prs

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

FAQPage Schema
How do I identify and manage stale open pull requests in GitHub?▼

You can identify and manage stale pull requests by running the /keel:stale-prs command, which detects quiet or drifted PRs, posts triage comments, and optionally rebases them to sync with the base branch.

What is the best way to triage GitHub PRs that have drifted from the base branch?▼

Triage drifted GitHub PRs by detecting those that have fallen behind the base branch, automatically posting comments with action suggestions, and optionally rebasing non-draft PRs to bring them up to date.

Can I preview stale PR triage actions before making changes to my repository?▼

Yes, you can use the Dry Run Mode to see exactly what triage and rebase actions would be taken on your stale pull requests without committing any changes to the repository.

Does this stale PR management tool work with draft pull requests?▼

The tool identifies all stale open pull requests, but the optional rebase feature specifically targets non-draft PRs to sync them with the base branch, leaving draft PRs untouched by rebasing.

Do I need GitHub API access to automate stale pull request rebase operations?▼

Yes, GitHub API access and appropriate project configuration are required to automate the identification, triage, commenting, and rebase operations for stale pull requests in your repositories.

Why does my GitHub repository have so many quiet pull requests and how can I get a summary?▼

Quiet pull requests accumulate when contributors stop updating them; this Skill detects them, takes triage actions, and provides a summary report of all actions taken for each PR.

Related Skills

Explore More Software Engineering Skills→
shellicarshellicar

github-repos

Configure GitHub repository settings and enforce branch protection rules via the gh CLI.

Community
Intermediate
llama-farmllama-farm
835

commit-push-pr

Stage changes, create conventional commits, push to origin, and open a PR via gh CLI.

Official
Advanced
magicpro97magicpro97
8

merge-when-green

Automatically merge GitHub pull requests after all required CI checks pass.

Community
Intermediate
aditriokaaditrioka

issue-burndown

Automate GitHub issue resolution and Pull Request creation via API.

Community
Advanced