Run NemoClaw live end-to-end tests, which check complete workflows, or inspect existing release evidence. Routes requests to local or trusted GitHub workflows and reports the tested commit, results, workflow link, and relevant job links.
Run or inspect NemoClaw live E2E evidence. Routes requested local execution, trusted GitHub dispatch, and release-evidence inspection.
Review the instructions the agent will receive before you install.
| Request | Procedure |
|---|---|
| Run working-tree source or a selected local commit | Local Runs |
| Run the latest PR commit on GitHub, including failure-triggered comparison with its exact base | Manual PR Runs |
Run the current main commit on GitHub | Main Runs and the Launchable boundary below |
| Inspect existing evidence for a release decision | Report the Release Context |
| Triage, diagnose, debug, or repair an E2E failure | Load Audit E2E Assertions; this skill still owns dispatch and run-level reporting. |
| Classify one failed GitHub Actions job | For E2E failures, use the assertion-audit route above. For other jobs, load nemoclaw-maintainer-classify-ci-failure. |
A new GitHub candidate run tests the latest PR commit or the current main commit.
Manual PR runs may replay the PR base after a candidate failure, as described in their procedure.
Report arbitrary historical candidate selection as unsupported. Preserve the workflow's identity and trust checks.
Push runs select change-relevant E2E and publish Relevant E2E; they do not always run the full
suite. Only a full manual run publishes Release qualification. That aggregate reports the full
suite; it does not decide whether a tag can proceed. A generic E2E request does not authorize
Exact staging Brev Launchable.
Use .github/workflows/e2e.yaml from trusted main for GitHub runs. Do not substitute local live
E2E unless the maintainer explicitly requests local execution. Do not load a dispatch reference for
a release inspection unless the maintainer requests a new run.
Read Staging Launchable before a dispatch that includes
Exact staging Brev Launchable. It owns the credential, deployment, cleanup, artifact, and queue
boundaries. A generic E2E request does not authorize that job.
Read Release Context to inspect the newest identifiable full
manual main run and report its commit, times, attempt, aggregate, and non-successful jobs.
This is read-only. The caller owns the release decision.
Return:
A focused run supplements the reported full-run status; it does not become a full run.
Do not ask for release confirmation or decide whether a release can proceed. The release-tag skill owns the general E2E decision and records any reason for proceeding with an exceptional general E2E status.
Follow the shared Git and GitHub Access Hard Stop.
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.