Cuiar
Sign inDownload

List pull requests that wait for review

Open PRs across your repos with age, reviewers and CI status, the oldest first.

  • On a schedule: Every weekday at 10:00
Use in CuiarRun from your AI agent

What it does

The task

List the open pull requests that are not drafts in these GitHub repositories: repos. For each one, give the title, the author, the age in days, the requested reviewers, the review status and the CI status. Mark the PRs that wait for a review for more than days days and the PRs with merge conflicts. Send me a table, the oldest first, with links. Do not comment, approve or merge.

  • It works in GitHub, in the workspace you pick, and signs in with passwords from your Cuiar vault.
  • As a routine it runs every weekday at 10:00 (cron 0 10 * * 1-5).

What you give it

BlankWhat to giveExample
reposThe repositories to check, separated by commasbrightleaf/web, brightleaf/api, brightleaf/sdk
daysDays after which a PR waits too long2

What you get back

An example run with the example values above. Your run uses your own data.

14 open PRs in 3 repos, 4 wait more than 2 days

PRAuthorAgeReviewersReviewCI
web#821 Move billing to the new APIAisha6 dTom, LeoNonePass
api#236 Rate limit per workspaceKofi4 dNadiaChanges requestedFail
web#826 Fix the date picker in SafariMia3 dTomNonePass, merge conflict
sdk#119 Retry on 429Sam3 dnoneNonePass

10 more PRs are 2 days old or newer.

Run it in Cuiar

  1. 01

    Open it

    Click Use in Cuiar on this page. The side panel opens with the task in the composer.

  2. 02

    Fill in 2 blanks

    Type repos and days. Tab moves to the next blank.

  3. 03

    Run it, then repeat it

    Run sends it once. To run it every weekday at 10:00, make a routine on cuiar.com/routines or with the CLI below.

As a routine, from the terminal

cuiar routines create "List pull requests that wait for review" --schedule "0 10 * * 1-5" --time-zone Europe/Berlin \
  "List the open pull requests that are not drafts in these GitHub repositories: brightleaf/web, brightleaf/api, brightleaf/sdk. For each one, give the title, the author, the age in days, the requested reviewers, the review status and the CI status. Mark the PRs that wait for a review for more than 2 days and the PRs with merge conflicts. Send me a table, the oldest first, with links. Do not comment, approve or merge."

Run it from your AI agent

Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.

1. Add Cuiar to Claude Code

claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp

2. Ask your agent

Use the Cuiar tool create_routine to run my "List pull requests that wait for review" template with repos = brightleaf/web, brightleaf/api, brightleaf/sdk; days = 2.

Setup for other agents: AI agents.

The tool call

{
  "name": "create_routine",
  "arguments": {
    "name": "List pull requests that wait for review",
    "task": "List the open pull requests that are not drafts in these GitHub repositories: brightleaf/web, brightleaf/api, brightleaf/sdk. For each one, give the title, the author, the age in days, the requested reviewers, the review status and the CI status. Mark the PRs that wait for a review for more than 2 days and the PRs with merge conflicts. Send me a table, the oldest first, with links. Do not comment, approve or merge.",
    "schedule": "0 10 * * 1-5",
    "time_zone": "Europe/Berlin"
  }
}

Related templates

All engineering templates

  • Engineering

    Sort the security alerts in your repositories

    Open Dependabot alerts across your repos, grouped by package, with the fix version and any open fix PR.

    On a schedule: Every Monday at 9:30
    • GitHub

  • EngineeringAsks first

    Write release notes from merged pull requests

    Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.

    You start it: When you start it
    • GitHub

  • Engineering

    Read the changelogs before you upgrade dependencies

    Breaking changes, security fixes and upgrade steps for each outdated package, from its release notes.

    You start it: When you start it
    • GitHub
    • npm
    • PyPI

  • EngineeringAsks first

    Label and sort new GitHub issues

    Labels, a priority and a possible duplicate for each new issue, applied after you approve them.

    On an event: When a new issue is opened
    • GitHub

  • Engineering

    Find flaky tests in your CI runs

    Tests that fail and then pass on the same commit, with the count and the error, from your recent runs.

    You start it: When you start it
    • GitHub
    • Google Sheets

  • Engineering

    Find why a deploy failed

    The error from the build log, the change that caused it and a suggested fix, sent when a deploy fails.

    On an event: When a deploy fails in Vercel
    • Vercel
    • GitHub