Answer NemoClaw maintainer questions using policy references covering issue and pull request assessment, labels, project fields, releases, and competing contributions. It explains the relevant rules in plain language through a read-only workflow.
Answer NemoClaw maintainer policy questions about triage, labels, Project fields, releases, or competing contributions. Read-only.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This package contains policy references. This file is its manifest and index.
Read the reference that owns the question. Read additional references only when that question crosses their boundaries.
needs:*, confidence, and suggestion payloads.agt: *, and release labels.Read the related reference before you answer or apply policy.
Use plain language for maintainers. Distinguish Issue Type, PR type labels, needs:* labels, Project fields, close reasons, and release labels.
Do not invent labels, statuses, fields, release labels, or workflow states.
Follow the shared Documentation Writing and Review
contract for changed workflow guidance and maintainer-facing text.
For agent implementation, use triage-instructions.md as the payload contract.
Use label-taxonomy.json to validate allowed values.
Workflow answers must remain reference-backed. Do not encode alternate policy in this manifest.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Publish or update a NemoClaw pull request and track automated checks and reviews through completion. It preserves the requested scope, coordinates repairs for valid findings, and reports the latest commit’s results and remaining blockers.
Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.
Prepare a local NemoClaw development environment, repair setup problems, or check readiness. It also handles explicitly requested command-line access, runtime onboarding, and launching the coding agent pinned by the project.
Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.
Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.
Update NemoClaw documentation after merged changes or audit it for outdated guidance. Verify current behavior against source and tests, edit the pages responsible for that guidance, and check affected links and generated variants.