OpenParable
Skip to content
← Back to skills

Who Blocks This PR

Productivity
who-blocks-this-pr

Who Blocks This PR is an Agent Skill for productivity published in the fleetdm/fleet repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Analyze a PR to determine which files still need approval and from whom, based on CODEOWNERS and website/config/custom.js. Use when the user asks "who needs to approve", "why is the PR blocked", "who blocks this PR", or similar.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/fleetdm/fleet/blob/HEAD/.claude/skills/who-blocks-this-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/who-blocks-this-pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

PR Approvals

Quickly determine which reviewers are still needed for a PR and which files they own.

Step 1: Get the blocking info from GitHub

Run these in parallel:

  • gh pr view <number> --json mergeStateStatus,mergeable,reviewDecision to check if it's actually blocked
  • gh api repos/<owner>/<repo>/pulls/<number> --jq '.requested_reviewers[].login' to get who GitHub is still waiting on
  • gh pr view <number> --json reviews --jq '.reviews[] | select(.state == "APPROVED") | .author.login' to see who already approved
  • gh pr view <number> --json files --jq '.files[].path' to get changed files

If the PR is not blocked, just report that and stop.

Step 2: Map requested reviewers to files

IMPORTANT: Distinguish between blocking and non-blocking reviewers.

  • CODEOWNERS (repo root) creates required/blocking reviews. GitHub's branch protection enforces these. Last matching pattern wins.
  • website/config/custom.js githubRepoDRIByPath and githubRepoMaintainersByPath auto-request reviewers but do NOT block merges. These are courtesy requests.

For each still-requested reviewer, check whether they are required by a CODEOWNERS pattern that matches a changed file. If they only appear in custom.js, they are requested but not blocking.

Step 3: Report concisely

Output two sections:

Blocking (CODEOWNERS-required):

  • Who is still needed, and which files/patterns require their approval

Requested but not blocking (custom.js DRI):

  • Who was auto-requested, and for which files -- note these don't block the merge

Also note who has already approved and what they covered.

Do NOT give a full breakdown of every file's ownership. Only show what's relevant to the still-requested reviewers.