skills.rest
NVIDIA
NVIDIAOFFICIAL
Explore all skills by this author →
WebsiteGitHub

nemoclaw-maintainer-verify-stale

Verifies whether stale NemoClaw bug reports still reproduce on the newest release tag.

22.3k|3.1k|Updated Mar 15, 2026
Search Tags:#issue triage#reproduction#bug verification#gitHub#release testing#brev#NemoClaw
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-verify-stale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-verify-stale
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-verify-stale
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-verify-stale

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Maintainers of the NVIDIA/NemoClaw repository accumulate stale bug reports whose status on current releases is unknown. This Skill automates the verification loop: it selects old Bug-type issues, reproduces them on the reported release, re-tests on the newest release tag, and prepares an evidence-backed comment and Project update for maintainer approval.

Core Features & Use Cases

  • Candidate selection and filtering: Queries open issues via GitHub GraphQL, filters by native Issue Type, platform, security, and idempotency markers, and parses the reported version from labels or body text.
  • Safe reproduction on Brev instances: Treats issue reproducers as untrusted input, builds a bounded reviewed reproducer, provisions or reuses Brev CPU/GPU instances with a 60-minute budget, and validates the reported release before testing the newest tag.
  • Evidence-backed verdicts with approval gates: Scores confidence, redacts transcripts, drafts concise comments (fixed-on-latest, still-reproduces, by-design, verify-inconclusive), and never writes to GitHub or closes issues without explicit maintainer approval.
  • Use Case: A maintainer asks to drain the bug backlog; the Skill verifies issue #2604 against v0.0.34, confirms the bug is fixed, and proposes a tag-anchored comment with linked evidence.

Quick Start

Ask the agent to verify whether stale NemoClaw bug issue number 2604 still reproduces on the newest release tag.

Frequently Asked Questions about nemoclaw-maintainer-verify-stale

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

FAQPage Schema
How do I verify stale GitHub bug reports automatically?▼

Provide an issue number or request batch mode; the Skill selects Bug-type issues, parses the reported version, reproduces the bug on that release, then re-tests on the newest release tag. It drafts an evidence-backed comment and Project update that requires maintainer approval before posting.

How does the Skill reproduce bugs without risking the maintainer's machine?▼

Issue reproducers are treated as untrusted input and rebuilt as bounded reviewed scripts. Execution happens on dedicated or reused Brev cloud instances with a 60-minute budget, credential isolation, and automatic cleanup, never directly from issue text.

Can it verify bugs on Windows, macOS, or Jetson platforms?▼

No. Version 1 only supports Brev-reproducible Linux targets such as Ubuntu, DGX Spark, and GB10. Issues labeled windows, wsl, macos, jetson, or n1x are skipped because Brev has no equivalent hardware.

Does the Skill ever close issues or write to GitHub automatically?▼

Never. It never auto-closes issues, never substitutes labels for Issue Type, and never posts comments or updates Project fields before the maintainer explicitly approves the proposed write set.

What happens when a bug requires a hosted provider API key?▼

The Skill stops and prompts the maintainer to either approve a temporary 0600 credential file on a dedicated Brev instance, substitute Ollama with an inconclusive verdict, or skip the issue. Credentials never appear on command lines.

Why does a verification return verify-inconclusive instead of fixed?▼

A fixed verdict requires the same reviewed reproducer to first expose the symptom on the reported release. Baseline install failures, provider substitution, unsupported platforms, or missing evidence all produce verify-inconclusive instead.

Related Skills

Explore More Software Engineering Skills→
cropsggcropsgg
15

triage

Assign type, priority, reproduction status, and routing to GitHub issues.

Community
Intermediate
RDEWAIRDEWAI
5

approve-stories

Validate and update sprint backlogs to Approved status with metadata changes.

Official
Intermediate
4e696b6f4e696b6f

clawsec-env

Scan repositories for credential exposure risks and missing security configurations.

Community
Intermediate
stackroxstackrox

test

Run unit and integration tests to verify bug fixes and document results.

Official
Advanced