nemoclaw-maintainer-find-review-pr

Find open security and priority-high PRs and link them to issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers spend excessive time identifying open PRs that require review, especially those related to security and high-priority issues, and linking them to their target issues.

Core Features & Use Cases

  • Find open PRs labeled security and priority-high across a repository.
  • Link each PR to its referenced issue and detect duplicates where multiple PRs address the same issue.
  • Present a clean, review-ready summary table to decide which PRs to review, merge, or close.
  • Use Case: A maintainer runs this to quickly surface top security-related PRs needing attention.

Quick Start

Trigger the maintainer workflow to surface review candidates for the current repository.

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 duplicate pull requests addressing the same GitHub issue?

To find duplicate pull requests linked to the same GitHub issue, this Skill parses PR metadata and body text to map PRs to issues, then groups results by issue to surface duplicate and superseded relationships in a summary table.

How do I triage open GitHub PRs labeled security and priority-high?

Triage open GitHub PRs labeled security and priority-high by triggering the maintainer workflow, which queries the repository via GitHub CLI and builds a decision-ready summary table linking each PR to its referenced issue.

Can I detect superseded PR relationships using GitHub CLI?

Yes, you can detect superseded PR relationships using GitHub CLI by parsing PR metadata and body text to map PRs to issues, grouping results to identify when multiple PRs address the same issue.

Does this PR duplicate detection approach work without extra dependencies?

This PR duplicate detection approach works with GitHub CLI access and requires no extra dependencies, parsing PR metadata and body text directly to map PRs to issues and group results.

What's the best way to link security pull requests to their target issues?

The best way to link security pull requests to their target issues is parsing PR metadata and body text to map PRs to issues, grouping results to build a review-ready summary table for maintainers.

When should I not use automated PR triage for GitHub repositories?

Automated PR triage for GitHub repositories is not suitable when you lack GitHub CLI access or need to analyze PRs without labels, as this Skill specifically filters for PRs labeled security and priority-high.