NemoClaw Maintainer Day

The first script determines the target version. The second shows shipped vs open.

Step 2: Pick One Action

From the open version-targeted items, pick the highest-value one:

1. Ready-now PR — green CI, no conflicts, no major CodeRabbit, has tests → follow MERGE-GATE.md
2. Salvage-now PR — close to ready, needs small fix → follow SALVAGE-PR.md
3. Security item — touches risky areas → follow SECURITY-SWEEP.md
4. Test-gap item — risky code with weak tests → follow TEST-GAPS.md
5. Hotspot cooling — repeated conflicts → follow HOTSPOTS.md
6. Sequencing needed — too large for one pass → follow SEQUENCE-WORK.md

If all version-targeted items are blocked, fall back to the general backlog. Productive work on non-labeled items is better than waiting.

Prefer finishing one almost-ready contribution over starting a new refactor.

Step 3: Execute

Follow the chosen workflow document. A good pass ends with one of:

• a PR approved, a fix pushed, a test gap closed, a hotspot mitigated, or a blocker surfaced.

Step 4: Report Progress

Re-run the progress script and show the update:

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>

If all version-targeted items are done, suggest running /nemoclaw-maintainer-evening early.

Update .nemoclaw-maintainer/state.json via the state script:

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history <action> <item> "<note>"

Commit Hygiene

The prek "Regenerate agent skills from docs" hook auto-stages .agents/skills/ files. Before every git add and git commit on a PR branch, run git reset HEAD .agents/skills/nemoclaw-maintainer-* to unstage them. Only commit skill files in dedicated skill PRs.

Stop and Ask When

• Broad refactor or architecture decision needed
• Contributor intent unclear and diff would change semantics
• Multiple subsystems must change for CI
• Sensitive security boundaries with unclear risk
• Next step is opening a new PR or merging

/loop Integration

Designed for /loop 10m /nemoclaw-maintainer-day. Each pass should produce compact output: what was done, what changed, what needs the user. Check state.json history to avoid re-explaining prior context on repeat runs.