nemoclaw-contributor-onboard

Prepares a NemoClaw source checkout for compliant contribution using the repository setup script and readiness doctor.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New contributors to the NemoClaw repository often struggle with configuring a development machine correctly—installing dependencies, setting up Git hooks, configuring commit signing, and verifying readiness before a first PR. This Skill routes all of that through the repository's own setup script and doctor, avoiding duplicated or drifting setup logic. ## Core Features & Use Cases - Intent-based routing: Distinguishes readiness checks (--doctor), initial setup, explicit repair (--repair), CLI exposure (--expose-cli), and runtime onboarding (--with-runtime) so only the requested action runs. - Trust-first execution: Reviews the checkout diff against trusted origin/main before running any checkout-local code, and requires explicit approval for host-level changes like package installs, GitHub auth, or signing keys. - First-PR guidance: Explains the Conventional Commits workflow, DCO sign-off, commit signing, and PR template requirements before implementation begins. - Use Case: A new contributor clones NemoClaw and asks their coding agent to set up the machine. The agent reads AGENTS.md and CONTRIBUTING.md, runs ./scripts/dev-setup.sh, fixes any doctor-reported issues with approval, and confirms readiness for a first PR. ## Quick Start Use the nemoclaw-contributor-onboard skill to set up this machine as a NemoClaw contributor and verify it is ready for a first PR.

Frequently Asked Questions about nemoclaw-contributor-onboard

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

FAQPage Schema
How do I set up a NemoClaw development machine for my first PR?

Run ./scripts/dev-setup.sh from the repository root after reading AGENTS.md and CONTRIBUTING.md. The script handles dependencies, builds, and Git hooks; then run the doctor mode to confirm readiness before starting your first PR.

How do I check if my NemoClaw contributor setup is ready?

Run ./scripts/dev-setup.sh --doctor for a readiness-only check without modifying anything. Use --doctor --json when you need a machine-readable report of the readiness status.

When should I use dev-setup.sh --repair instead of the default setup?

Use --repair only when explicitly asked to repair or retry repository-local setup, such as broken dependencies, builds, or hooks. For host, account, or signing issues, fix those first and rerun the doctor instead of rerunning setup.

Does NemoClaw contributor setup require runtime onboarding with a sandbox?

No, runtime onboarding via --with-runtime is optional and only needed when the intended issue requires a live gateway or sandbox. Documentation work and isolated unit tests normally do not require it.

What commit and PR requirements does NemoClaw enforce for contributors?

Commits must use Conventional Commits in <type>(<scope>): <description> form and be signed so they appear as Verified on GitHub. The PR description must include a Signed-off-by line for DCO compliance and follow the repository's pull request template.