<!-- 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