nemoclaw-maintainer-cross-issue-sweep

Scan open GitHub issues to find adjacent fixes and conflicts for a pull request.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-cross-issue-sweep-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-cross-issue-sweep
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-cross-issue-sweep
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-cross-issue-sweep-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? During PR review, maintainers often miss that a pull request also resolves other open issues or conflicts with behavior requested elsewhere, leading to duplicate work and merge-time surprises. ## Core Features & Use Cases - Fingerprint Extraction: Pulls changed files, symbols, and error strings from a PR diff using the GitHub CLI. - Candidate Search and Classification: Searches open issues across three dimensions, then classifies each as ADJACENT_FIX, CONTRADICTING, SAME_ISSUE_DIFF, or UNRELATED with cited evidence. - Evidence-Based Reporting: Renders a markdown report with confidence levels, reverse-link boosts, and suppressed-candidate counts. - Use Case: Before merging a bugfix PR, run the sweep to discover that it also closes issue #4521 and contradicts the opt-in behavior requested in issue #4187, so you can update the PR body and coordinate with stakeholders. ## Quick Start Ask the agent to run the cross-issue sweep on PR #2851 and report any adjacent fixes or contradicting issues with evidence.

Frequently Asked Questions about nemoclaw-maintainer-cross-issue-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find GitHub issues that a pull request also fixes?

Run the sweep on the PR number to extract its changed files, symbols, and error strings, then search open issues across those dimensions. Each candidate is classified as ADJACENT_FIX only when diff lines and issue symptoms can be cited as evidence.

How to detect PR conflicts with open issues before merging?

The sweep classifies candidates as CONTRADICTING when the PR prevents behavior another issue requests, using direct, by-omission, or follow-on evidence. Results are filtered to medium and high confidence and rendered in a report for maintainer review.

What tools are required to run a cross-issue scan on a repository?

An authenticated GitHub CLI (gh) is required, along with a target repository containing open issues and an open PR to scan. The scripts use gh search issues and gh issue view to gather candidates.

Can the issue search be customized for a different repository?

Yes, edit repo-policy.md to change search caps, per-language symbol extraction regexes, bot-author exclusions, and the confidence threshold. The defaults follow NemoClaw conventions but support TypeScript, Python, Go, and shell patterns.

What are the limitations of automated issue-PR relationship detection?

The sweep does not run PR code against adversarial inputs, perform static analysis with tools like CodeQL or Semgrep, or disambiguate symbols with machine learning. Low-confidence and evidence-free matches are filtered out by default.