Skills

Nemoclaw Maintainer Find Review PR

Find high-priority open NemoClaw security PRs to review, including competing or...

Install

npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-find-review-pr -g -a claude-code -y
Repository
NVIDIA/NemoClaw22.9k
Category
Security
Updated
3d ago
License
Apache-2.0
Context cost
Mediumabout 1,510 tokens
Runs scripts
No, instructions only

What it does

Find high-priority open NemoClaw security PRs to review, including competing or superseded candidates.

<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 -->

Find PR to Review

Find open PRs with the security label and Project Priority Urgent or High. Link each PR to its issue. Identify competing or superseded PRs. Report the results for the maintainer.

Prerequisites

  • gh (GitHub CLI) must be installed and authenticated.
  • The active gh token must have read:project scope.
  • You must be in a GitHub repository (or the user must specify OWNER/REPO).

Step 1: Fetch candidate PRs

Read the NemoClaw Development Tracker and select open PRs that carry the canonical security label and have Project Priority Urgent or High:

gh project item-list 199 --owner NVIDIA --limit 1000 --format json \
  | jq '[.items[]
    | select(.content.repository == "NVIDIA/NemoClaw")
    | select(.content.type == "PullRequest")
    | select(((.labels // []) | index("security")) != null)
    | select(.priority == "Urgent" or .priority == "High")
    | {number: .content.number, title: .content.title, url: .content.url,
       priority: .priority, status: .status}]'

Remove entries for closed PRs. For each remaining PR, fetch the body, author, branch, labels, and creation time with gh pr view. If no PRs remain, report that result and stop.

Step 2: Extract linked issues

For each PR, search its body for issue references. Match these patterns without case sensitivity:

  • Fixes #NNN, Closes #NNN, Resolves #NNN, Refs #NNN, Relates to #NNN, or Part of #NNN
  • Related issues / Linked issues section containing #NNN
  • Issue number in the PR title, such as a (#NNN) suffix
  • Branch name containing an issue number, such as fix/something-NNN

Build a mapping: PR# → [issue numbers].

If a PR has no detectable linked issue, mark it as (no linked issue).

Step 3: Detect duplicates

Read the whole SKILL.md on GitHub

More in Security