nemoclaw-maintainer-cross-issue-sweep

To find out if a GitHub pull request fixes multiple open issues, you can perform a cross-issue sweep that fingerprints the PR diff to search for adjacent issues with matching touched files and symbols. This identifies bundle-fix opportunities using evidence-based classification.

Regression risk detection in pull request review identifies contradiction risks by checking if a PR's diff unintentionally breaks or conflicts with expectations described in other open issues. It classifies these conflicts using cited PR diff lines and issue symptoms to prevent hallucinated matches.

You check for contradiction risks before merging a GitHub PR by running a cross-issue sweep that fingerprints the diff and metadata, then classifies candidate issues as ADJACENT_FIX, CONTRADICTING, SAME_ISSUE_DIFF, or UNRELATED. The output report highlights conflicts with file:line references and suggested next actions.

Yes, you need authenticated GitHub CLI access to run a cross-issue sweep on a pull request. The process requires an open PR number and uses deterministic scripts for fingerprinting, searching, and rendering reports alongside LLM judgment constrained by cited evidence.

Evidence-based classification prevents false matches in issue triage by requiring cited PR diff lines and issue symptoms to support any ADJACENT_FIX or CONTRADICTING judgment. This strict four-class system avoids hallucinated matches by demanding concrete file:line and symptom references.