nemoclaw-maintainer-find-review-pr

Group open security-labeled GitHub pull requests by linked issues for review.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-maintainer-find-review-pr-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-find-review-pr
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NemoClaw/nemoclaw-maintainer-find-review-pr
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-maintainer-find-review-pr-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of maintainers missing the best next pull request to review by surfacing open high-priority security PRs, linking them to the issues they address, and highlighting duplicates or superseded work.

Core Features & Use Cases

  • Targets high-signal PRs: Filters open PRs to those labeled security and priority: high and summarizes key metadata for review decision-making.
  • Links PRs to issues: Extracts referenced issue numbers from PR bodies (e.g., Fixes/Closes/Resolves and common “linked issue” patterns, title hints, or branch naming).
  • Detects duplication and supersession: Groups multiple PRs working on the same issue to flag duplicates, and flags PRs that appear to replace/fold in another open PR to avoid redundant review effort.
  • Use case: As a maintainer triaging security fixes, quickly identify which PR(s) map to which issues, compare competing implementations, and decide what to review first or what to close.

Quick Start

Use the skill to find all open security + priority: high PRs and produce a prioritized review table with duplicate and superseded groups.

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?

To find high-priority security pull requests for review, you can filter open GitHub PRs by the `security` and `priority: high` labels. This surfaces critical fixes and summarizes key metadata to help maintainers quickly decide what to review first.

How does issue tracking link duplicate pull requests during security triage?

Issue tracking links duplicate pull requests by extracting referenced issue numbers from PR bodies, titles, and branches. It groups multiple PRs targeting the same issue to flag duplicates and identify superseded security work during triage.

What is the best way to deduplicate competing GitHub pull requests fixing the same issue?

The best way to deduplicate competing GitHub pull requests is by grouping open PRs that reference the same linked issue. This detects duplication and supersession, allowing maintainers to compare implementations and avoid redundant review effort.

Do I need GitHub CLI authentication to track open security pull requests?

Yes, you need GitHub CLI authentication to track open security pull requests. The label filtering, issue-reference extraction, and duplicate grouping processes require authenticated access to your repository's PR and issue data.

Can this detect superseded work among currently open GitHub pull requests?

Yes, this can detect superseded work among currently open GitHub pull requests. It flags PRs that appear to replace or fold in another open PR targeting the same linked issue, preventing redundant code review during maintenance.

When should I use automated PR deduplication for maintainer workflow?

You should use automated PR deduplication for maintainer workflow during repository maintenance and security triage. It is ideal when you have multiple open priority high security PRs and need to select the next candidate while avoiding redundant reviews.