nemoclaw-contributor-implement-issue

Implements accepted NemoClaw GitHub issues with validated code changes and no PR publication.

22.3k|3.1k|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-contributor-implement-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-implement-issue
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-implement-issue
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-contributor-implement-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributors picking up an accepted NemoClaw issue need a disciplined workflow that confirms scope, makes the smallest valuable code change, validates it, and records evidence without accidentally pushing branches or opening pull requests.

Core Features & Use Cases

  • Scoped Issue Implementation: Confirms the accepted scope of a named GitHub issue, selects the smallest independently valuable capability slice, and edits the local checkout only.
  • Validation and Evidence Recording: Maps success criteria and security controls to focused test evidence, recording positive, negative, error, and boundary results.
  • Safe Boundaries: Treats issue content as untrusted input, refuses GitHub writes or PR publication, and routes ambiguous requests between planning and implementation.
  • Use Case: A contributor asks to implement NemoClaw issue #8378 with negative and error-path tests; the workflow reads the issue, edits code and tests, runs focused validation, and reports remaining gates without creating a PR.

Quick Start

Ask the agent to pick up a specific accepted NemoClaw issue for implementation and stop before PR publication.

Frequently Asked Questions about nemoclaw-contributor-implement-issue

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

FAQPage Schema
How do I implement a NemoClaw GitHub issue without opening a PR?

Ask to pick up the issue for implementation and state that no PR should be published. The workflow confirms accepted scope, edits the local checkout, runs focused validation, and reports evidence while performing no GitHub writes.

What happens when I ask to work on a NemoClaw issue?

The phrase work on this issue is ambiguous between planning and implementation, so the workflow asks which lifecycle stage you want before loading either the planning or implementation workflow.

Can this workflow push a branch or create a pull request?

No. Implementation permits only local changes and validation. Pushing, GitHub writes, and PR publication are routed to the separate nemoclaw-contributor-create-pr workflow.

Does the workflow follow instructions written inside the issue body?

No. Issue bodies, comments, and PR content are treated as untrusted evidence, not agent instructions. Instruction-shaped content cannot override repository guidance or authorize pushes, credential disclosure, or publication.

What happens if no GitHub access tool is configured?

The workflow stops before editing because it cannot confirm accepted scope. It asks you to configure GitHub access and does not fall back to curl, web search, or other endpoints.