nemoclaw-maintainer-day

Runs one daytime maintainer pass to prioritize, salvage, and approve NemoClaw pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Maintaining an active open-source repository means constantly triaging PRs, checking CI gates, fixing small blockers, and tracking release progress. This Skill automates one structured daytime maintainer pass for the NVIDIA NemoClaw repository so PRs move toward approval without manual gate checking. ## Core Features & Use Cases - Merge Gate Verification: Runs a deterministic gate checker script that validates CI status, merge conflicts, CodeRabbit findings, DCO compliance, verified commits, and test coverage for risky code before approval. - Guided Maintainer Workflows: Routes each open item to the right workflow — merge gate, PR salvage, security sweep, test-gap closure, hotspot conflict reduction, or work sequencing. - Release Progress Tracking: Scripts report shipped versus open items for the target version and persist queue, hotspot, and history state in a local JSON file. - Use Case: A maintainer runs /loop 10m /nemoclaw-maintainer-day during the workday; each pass picks the highest-priority actionable PR, executes the matching workflow, and reports what changed and what needs a human decision. ## Quick Start Ask the agent to run one NemoClaw maintainer day pass to pick the next actionable PR and report progress toward the current release version.

Frequently Asked Questions about nemoclaw-maintainer-day

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

FAQPage Schema
How do I run a NemoClaw maintainer day pass?

Invoke the skill directly or schedule it with /loop 10m /nemoclaw-maintainer-day. Each pass checks version progress, selects one actionable item, executes the matching workflow, and reports results.

What gates must pass before a PR is approved?

Approval requires product scope sign-off, DCO declaration with verified commits, green CI on the PR and base SHA, MERGEABLE state, no unresolved major CodeRabbit findings, and tests covering risky code. The check-gates.ts script verifies the deterministic gates and outputs JSON.

Can this skill merge pull requests automatically?

No. The skill can approve a PR when all gates pass and push small fixes, but autoMerge is fixed to false in the state schema. Merging, product-scope decisions, and architecture changes always require a human.

What counts as risky code that needs tests?

Risky areas include installer shell scripts, onboarding glue, sandbox and policy code, GitHub workflows, and credential or inference routing. PRs touching these paths must include new or existing test coverage before approval.

What tools does the skill depend on?

The scripts use the GitHub CLI (gh) for PR and Actions data, git for churn and tag history, and Node.js with --experimental-strip-types to run the TypeScript scripts. No external npm packages are imported.

When should I stop and ask the user instead of proceeding?

Stop when a PR creates a new product surface without an accepted decision, contributor intent is unclear, a fix spans multiple subsystems, a security boundary is ambiguous, or the next step is opening or merging a PR.