nemoclaw-maintainer-pr-comparator

Compare competing pull requests for one issue and recommend a merge candidate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When two or more open pull requests address the same GitHub issue, maintainers must manually compare eligibility, correctness, and quality across each PR before deciding which to merge. This Skill automates that comparison with tiered gates, weighted scoring, and a deterministic verdict report. ## Core Features & Use Cases - Tiered evaluation pipeline: Runs six Tier 0 eligibility gates (open state, CI on PR SHA, mergeability, DCO and verified-commit compliance, branch protection, resolved automated-review threads), six Tier 1 correctness checks, and four Tier 2 quality checks with weighted scoring. - Supersession and attribution handling: Parses PR bodies for supersession statements, classifies transferred work, and enforces contributor attribution before recommending a replacement PR. - Deterministic verdict rendering: Validates the comparison spec and renders a markdown scorecard, behavior-coverage matrix, and merge or salvage recommendation via a Python renderer. - Use Case: An issue has three competing PRs. Run the comparator to discover candidates, gate them on CI and compliance, score their tests and quality, and receive a verdict naming the PR to merge or the one closest to ready. ## Quick Start Ask the agent to compare the open pull requests for a specific issue number in your repository and recommend which one to merge.

Frequently Asked Questions about nemoclaw-maintainer-pr-comparator

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

FAQPage Schema
How do I compare two pull requests for the same GitHub issue?

Run the comparator workflow with the issue number. It discovers candidate PRs, applies six Tier 0 eligibility gates, scores correctness and quality checks, and renders a verdict naming the PR to merge or the one closest to ready.

What eligibility gates must a pull request pass before merge recommendation?

Six Tier 0 gates are required: PR state open, CI green on the PR SHA, mergeable with clean state, contributor compliance (PR-body DCO declaration and GitHub Verified commits), branch protection approval, and resolved automated-review threads.

Does the comparator handle superseded pull requests and attribution?

Yes. It parses PR bodies for supersession statements like supersedes or closes in favor of, classifies work as independent, transferred, or unclear, and blocks a winner recommendation until required attribution such as cherry-pick sign-off or Co-authored-by trailers is verified.

What happens when no pull request passes all eligibility gates?

The skill enters degraded mode. It ranks eligible PRs by distance-to-ready using trivial versus substantive failure classification, leaves the winner null, and sets closest_to_ready only for an open, contributor-compliant PR.

What are the limitations of automated PR comparison?

The skill does not run PR code against adversarial inputs, scan other issues for related behavior, simulate reverts, or run static analyzers like CodeQL or Semgrep. Cross-issue evidence requires running the separate cross-issue sweep skill.