Prepare a daily NemoClaw maintenance plan by ranking pending pull requests and issues, checking work carried over from earlier versions, and selecting release targets. Produce a queue with owners, next actions, and merge readiness.
Prepare the NemoClaw morning maintainer plan: triage the backlog, select a target version, and identify release candidates and stragglers.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Start the day: triage, pick a version target, label items, share the plan.
See PR-REVIEW-PRIORITIES.md for the daily cadence and review priorities.
node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
This fetches tags, computes the next patch version, and finds open items still carrying older version labels. Surface stragglers first — they indicate post-tag housekeeping was interrupted or an item slipped across multiple cycles. Decide whether to relabel them to today's target or defer them out of the daily release flow.
Run the triage script to rank the full backlog:
node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts --approved-only
If too few results, run without --approved-only. The script fetches open PRs through gh, reads Project 199 Priority, enriches candidates with review, CI, file, and risky-area data, and applies the scoring model documented in PR-REVIEW-PRIORITIES.md.
Also use find-review-pr to surface security PRs whose Project Priority is Urgent or High. Merge these into the candidate pool.
Present the ranked queue to the user. After they confirm which items to target, label them:
gh label create "<version>" --repo NVIDIA/NemoClaw --description "Release target" --color "1d76db" 2>/dev/null || true
gh pr edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"
gh issue edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"
Pipe triage output into state:
node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts \
| node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts set-queue
Output the daily plan:
| Target | Item | Type | Owner | Next action |
|---|---|---|---|---|
| v0.0.8 | #1234 | PR | @author | Run merge gate |
| v0.0.8 | #1235 | Issue | unassigned | Needs PR |
Include: total items targeted, how many are PRs vs issues, how many are already merge-ready.
/nemoclaw-maintainer-day during the day to execute.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.