Skip to content
cccskills
FreePublished on GitHub

nemoclaw-maintainer-cross-issue-sweep

Find open issues affected by a proposed code change. Identify additional problems it may fix or requested behavior it may conflict with, then report supporting code differences, issue symptoms, and confidence levels.

OriginalShow the original description

Find open issues that a NemoClaw PR may also fix or conflict with. Use when related-issue analysis is requested.

NVIDIA/NemoClaw

Run score Not tested

See how to install

Good for

  • Find other open issues a PR may resolve
  • Check whether a PR conflicts with requested behavior
  • Prepare evidence for related-issue reviews
  • Report findings with confidence levels

Files included (10)

  • SKILL.md3.5 KB
  • checks/fingerprint-extraction.md2.0 KB
  • checks/relationship-judgment.md3.1 KB
  • relationship-rules.md3.6 KB
  • repo-policy.md1.7 KB
  • scripts/extract-fingerprint.sh5.8 KB
  • scripts/render-report.py4.3 KB
  • scripts/search-candidate-issues.sh3.3 KB
  • templates/report.md1.8 KB
  • validation/backtest.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Cross-Issue Regression Sweep

Find open issues that a PR can affect in addition to its linked issue. Report two relationship types:

  • Adjacent fix — The PR can also resolve another issue.
  • Conflict — The PR can prevent the behavior that another issue requests.

Prerequisites

  • gh CLI authenticated
  • A target repository with open issues
  • An open PR to scan

Repo policy

The defaults use NemoClaw conventions. Edit repo-policy.md for another repository.

Workflow

Step 1: Extract fingerprint

scripts/extract-fingerprint.sh <pr-number>

The script collects changed files, changed symbols, error strings, and the linked issue. See checks/fingerprint-extraction.md.

Step 2: Search candidate issues

scripts/search-candidate-issues.sh <fingerprint-json>

Search these three inputs. Keep no more than 30 candidates:

  • Per symbol: top 10 by recency
  • Per file path: top 5 by recency
  • Per error string: top 5 by recency

Remove duplicates and the linked issue.

Step 3: Classify each candidate

Classify each candidate with the rules in checks/relationship-judgment.md:

  • ADJACENT_FIX — The PR can resolve this issue.
  • CONTRADICTING — The PR conflicts with the requested behavior.
  • SAME_ISSUE_DIFF — same root bug as PR's primary issue (dedup filter)
  • UNRELATED — no meaningful relationship

For ADJACENT_FIX or CONTRADICTING, cite:

  • A PR diff line.
  • An issue symptom.
  • Confidence: high / medium / low

Classify the issue as UNRELATED if this evidence is not available.

Step 4: Reverse-link boost

Increase confidence by one level if the issue body or comments mention the PR number.

Step 5: Filter

  • Remove UNRELATED and SAME_ISSUE_DIFF results.
  • Remove low-confidence results.
  • Keep high- and medium-confidence ADJACENT_FIX and CONTRADICTING results.

Step 6: Render report

scripts/render-report.py < classifications.json

See templates/report.md for the format.

Reference files

Scripts

  • scripts/extract-fingerprint.sh — symbols, paths, and error strings
  • scripts/search-candidate-issues.sh — GitHub Search wrapper, dedupe, cap
  • scripts/render-report.py — report renderer

Composition with other skills

This skill is an optional follow-up to nemoclaw-maintainer-pr-comparator. The comparator does not run this skill or use its findings in the score. Run this skill when a maintainer asks for related-issue evidence. Report the evidence separately.

Limits

The skill does not:

  • run PR code against adversarial inputs
  • trace data flow with a static analyzer such as CodeQL or Semgrep
  • disambiguate symbols across codebases with a machine-learning model

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

nemoclaw-contributor-create-pr

FreeSummary

Publish or update a NemoClaw pull request and track automated checks and reviews through completion. It preserves the requested scope, coordinates repairs for valid findings, and reports the latest commit’s results and remaining blockers.

  • Publishing implemented changes as a pull request
  • Updating an open pull request after review feedback
  • Tracking automated checks and reviews on the latest commit
NVIDIA/NemoClaw22.8KUpdated Oct 23, 2026

nemoclaw-contributor-implement-issue

FreeSummary

Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.

  • Implement an accepted issue within its agreed scope
  • Repair a classified pull request finding
  • Validate failure, recovery, and cleanup behavior
NVIDIA/NemoClaw22.8KUpdated Oct 23, 2026

nemoclaw-contributor-onboard

FreeSummary

Prepare a local NemoClaw development environment, repair setup problems, or check readiness. It also handles explicitly requested command-line access, runtime onboarding, and launching the coding agent pinned by the project.

  • Setting up a local NemoClaw development environment
  • Checking readiness before starting development
  • Repairing local dependency, build, or hook problems
NVIDIA/NemoClaw22.8KUpdated Oct 23, 2026

nemoclaw-contributor-plan-issue

FreeSummary

Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.

  • Plan implementation for a named issue
  • Divide a large change into useful steps
  • Define acceptance criteria and test evidence
NVIDIA/NemoClaw22.8KUpdated Oct 23, 2026

nemoclaw-contributor-update-dependencies

FreeSummary

Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.

  • Assess the impact of a dependency upgrade
  • Plan migrations for a Hermes upgrade
  • Verify base images and selected artifacts
NVIDIA/NemoClaw22.8KUpdated Oct 23, 2026

nemoclaw-contributor-update-docs

FreeSummary

Update NemoClaw documentation after merged changes or audit it for outdated guidance. Verify current behavior against source and tests, edit the pages responsible for that guidance, and check affected links and generated variants.

  • Catch up documentation after merged changes
  • Audit documentation for outdated guidance
  • Update guides for changed user behavior
NVIDIA/NemoClaw22.8KUpdated Oct 23, 2026

See all skills by NVIDIA

Report a problem with this skill