nemoclaw-maintainer-find-review-pr

Find open GitHub PRs labeled security and priority: high and detect duplicates.

22.1k|3.0k|Updated Mar 15, 2026

Search Tags:#security #github #pr-review #gh-cli #issue-linking #duplicate-pr #maintainer-tooling

One-click install

npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-find-review-pr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-find-review-pr
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-find-review-pr
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-find-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help maintainers identify the next pull request to review by finding open GitHub PRs labeled security and priority: high, linking them to their issues, detecting duplicate or superseding PRs, and presenting concise review candidates so human reviewers can decide without manual searching.

Core Features & Use Cases

Label-based discovery: Enumerates open PRs that carry both security and priority: high labels.
Issue association: Parses PR bodies, titles, and branch names to extract linked issue numbers and mark PRs with no linked issue.
Duplicate and supersede detection: Groups PRs by linked issue to highlight duplicates and flags PRs that supersede or fold in others.
Summary and recommendation: Produces tables of duplicate groups and clean review candidates and recommends which PR to review first based on age, check status, and diff size.
Use case: Security maintainers triaging prioritized fixes after a vulnerability disclosure.

Quick Start

Ask the skill to find PRs to review in the current repository while authenticated with the GitHub CLI.

Frequently Asked Questions about nemoclaw-maintainer-find-review-pr

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

FAQPage Schema

How do I find high-priority security pull requests to review on GitHub?▼

Yes, you can detect duplicate PRs by grouping pull requests by their linked issue numbers. This process highlights duplicate groups and flags PRs that supersede or fold in others competing for the same issue.

How do I link GitHub pull requests to their issues for triage?▼

Link GitHub pull requests to issues by parsing PR bodies, titles, and branch names to extract linked issue numbers. PRs with no linked issue are explicitly marked for manual review during triage.

Do I need the GitHub CLI to find and analyze pull requests for review?▼

The best way to prioritize PR reviews is by analyzing PR metadata to compare competing PRs for the same issue, evaluating age, check status, and diff size to recommend which PR to review first.

What limitations exist when using GitHub CLI to detect duplicate pull requests?▼

Limitations include requiring explicit OWNER/REPO context, gh CLI authentication, and the ability to run gh pr view. PRs lacking explicit issue links in bodies or titles may not group correctly for duplicate detection.