docs: add agent-ready NemoClaw maintainer workflow policies by wscurran · Pull Request #4857 · NVIDIA/NemoClaw

wscurran · 2026-06-05T18:24:48Z

Summary

Closes #4856.

Adds an agent-ready NemoClaw maintainer policy package under .agents/skills/nemoclaw-maintainer-policies/ and updates the repo's issue templates and skill catalog to use it.

Changes

Add a user-invocable maintainer policy skill with reference-backed workflow guidance.
Add reference docs for workflow policy, triage, label taxonomy, Project fields, daily flow, release train, and examples.
Add machine-readable label taxonomy for agent/app validation.
Update bug, feature, and docs issue templates to set native GitHub Issue Type.
Update the NemoClaw skills guide to include the maintainer policy skill.

Validation

Parsed issue template YAML.
Parsed maintainer policy skill frontmatter.
Validated label-taxonomy.json.
Confirmed no README, CONTRIBUTING, or .github/nvoss/community-manager changes are included.

Summary by CodeRabbit

New Features
- Added a read-only maintainer policy skill manifest exposing curated, reference-backed maintainer guidance.
Documentation
- Added comprehensive maintainer references: daily flow, triage instructions, label taxonomy, project workflow, release-train rules, and examples/dry-run guidance.
- Updated GitHub issue templates to streamline types/labels and broaden environment/hardware fields.

copy-pr-bot · 2026-06-05T18:24:51Z

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

coderabbitai · 2026-06-05T18:24:58Z

Need an answer fast? Review this PR in Change Stack to ask focused questions about the PR or a changed range.

📝 Walkthrough

Walkthrough

Adds an agent-ready NemoClaw maintainer policy skill with SKILL manifest, reference documents (workflow, triage, label taxonomy MD+JSON, project workflow, daily flow, release train, examples), updates the skills guide, and aligns GitHub issue templates to native Issue Type and current triage label.

Changes

Policy Package and Integration

Layer / File(s)	Summary
Policy Foundation and Manifest `.agents/skills/nemoclaw-maintainer-policies/SKILL.md`, `.agents/skills/nemoclaw-maintainer-policies/references/workflow-policy.md`	Introduces the policy skill manifest with metadata and routing guidance. Establishes the source-of-truth hierarchy: native GitHub Issue Type, triage instructions, label taxonomy, and Project fields. Defines authorization boundaries for agent writes and the permitted agent-owned label namespace.
Triage, Labeling Guidance, and Examples `.agents/skills/nemoclaw-maintainer-policies/references/triage-instructions.md`, `.agents/skills/nemoclaw-maintainer-policies/references/label-taxonomy.md`, `.agents/skills/nemoclaw-maintainer-policies/references/label-taxonomy.json`, `.agents/skills/nemoclaw-maintainer-policies/references/examples.md`	Specifies triage confidence thresholds, write eligibility rules, and the exact dry-run JSON output shape. Enumerates canonical label families, mutual exclusivity rules, and application constraints. Provides machine-readable taxonomy with canonical labels and enforcement rules. Demonstrates expected recommendation shapes for issue triage, PR handling, and agent-owned labeling with anti-examples.
Project Workflow, Daily Flow, and Release Management `.agents/skills/nemoclaw-maintainer-policies/references/project-workflow.md`, `.agents/skills/nemoclaw-maintainer-policies/references/daily-flow.md`, `.agents/skills/nemoclaw-maintainer-policies/references/release-train.md`	Defines Project Status as lifecycle state owner and enumerates allowed field values. Outlines the daily slate workflow, required agent reporting fields, and issue form type requirements. Describes the 8-step daily maintainer flow and priority lane ordering. Specifies PR ownership of release labels, carry-forward semantics, cutoff procedures, and label pruning eligibility.
Skill Catalog Registration `.agents/skills/nemoclaw-skills-guide/SKILL.md`	Registers `nemoclaw-maintainer-policies` in the maintainer skill bucket, updates the maintainer bucket count to 13, and updates role included-skill totals (User 9→10, Contributor 11→12, Maintainer 18→25).
Issue Template Alignment `.github/ISSUE_TEMPLATE/bug_report.yml`, `.github/ISSUE_TEMPLATE/doc_issue.yml`, `.github/ISSUE_TEMPLATE/feature_request.yml`	Updates bug, documentation, and feature request templates to use native GitHub Issue Type (`Bug`, `Documentation`, `Enhancement`) and align default labels to current `needs: triage` queue. Expands environment/hardware options in bug template and reformats feature Category dropdown to human-readable names.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels

area: docs, needs: review, documentation

Suggested reviewers

cv
prekshivyas

Poem

🐰 I hopped through docs with tidy paws,
Lined up labels, rules, and laws.
A manifest, examples, and daily plan,
For maintainers and agent clan—
Hooray, neat process—careful applause!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	The PR fulfills all acceptance criteria from issue `#4856`: maintainer policy package with SKILL.md and reference docs, user-invocable routing, issue template updates to use native GitHub Issue Type, machine-readable label taxonomy, and no legacy community-manager or README changes.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to the stated objectives: policy skill package, reference documentation, label taxonomy, issue template updates, and skills guide updates. No unrelated modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly and accurately describes the main change: adding agent-ready maintainer workflow policies for NemoClaw. It is concise, specific, and directly reflects the primary objective of the PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch codex/nemoclaw-community-governance

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

github-actions · 2026-06-05T18:58:35Z

PR Review Advisor

Findings: 0 needs attention, 2 worth checking, 0 nice ideas
Since last review: 0 prior items resolved, 0 still apply, 1 new item found

Review findings

🛠️ Needs attention

None.

🔎 Worth checking

Source-of-truth review needed: Canonical maintainer policy adoption across active skills: The advisor marked localized patch analysis as needs_followup.
- Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
- Evidence: `workflow-policy.md` says consumers must use this package for canonical write policy, while existing `.agents/skills/nemoclaw-maintainer-triage/SKILL.md` and its legacy `references/triage-instructions.md` still define old labels and output shape.
Canonical policy is not yet wired into active maintainer workflows (.agents/skills/nemoclaw-maintainer-policies/references/workflow-policy.md:57): The new package declares that consumers must use it for canonical write policy, but existing active maintainer skills still direct agents to legacy label lists and release-label meanings. For example, the existing triage skill still reads its own `references/triage-instructions.md`, which recommends legacy labels such as `bug`, `documentation`, `enhancement:*`, `status: needs-info`, `Platform: MacOS`, and broader provider labels. That conflicts with the new package's native Issue Type model, `needs: info`, lowercase `platform:*`, and canonical label taxonomy. Existing morning/find-review/stale-verification docs also still mention release labels or priority labels in ways that conflict with the new policy.
- Recommendation: Update the active maintainer skills that apply or recommend metadata to load the new `nemoclaw-maintainer-policies` references, or explicitly mark the old embedded triage/reference files as superseded so agents cannot keep using both policy sources.
- Evidence: New `workflow-policy.md` says consumers must use this package for canonical write policy. Nearby existing files still reference legacy rules: `.agents/skills/nemoclaw-maintainer-triage/SKILL.md` reads its own `references/triage-instructions.md`; that legacy reference lists `bug`, `enhancement:*`, `documentation`, `status: needs-info`, `Platform: MacOS`, and provider labels not present in the new taxonomy.

🌱 Nice ideas

None.

Consider writing more tests for

**Canonical maintainer policy adoption across active skills** — Add a static consistency check that every active maintainer skill performing metadata, label, project-field, triage, or release-label decisions links to `.agents/skills/nemoclaw-maintainer-policies/` or otherwise declares itself non-authoritative.. `workflow-policy.md` says consumers must use this package for canonical write policy, while existing `.agents/skills/nemoclaw-maintainer-triage/SKILL.md` and its legacy `references/triage-instructions.md` still define old labels and output shape.

Since last review details

Current findings:

Source-of-truth review needed: Canonical maintainer policy adoption across active skills: The advisor marked localized patch analysis as needs_followup.
- Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
- Evidence: `workflow-policy.md` says consumers must use this package for canonical write policy, while existing `.agents/skills/nemoclaw-maintainer-triage/SKILL.md` and its legacy `references/triage-instructions.md` still define old labels and output shape.
Canonical policy is not yet wired into active maintainer workflows (.agents/skills/nemoclaw-maintainer-policies/references/workflow-policy.md:57): The new package declares that consumers must use it for canonical write policy, but existing active maintainer skills still direct agents to legacy label lists and release-label meanings. For example, the existing triage skill still reads its own `references/triage-instructions.md`, which recommends legacy labels such as `bug`, `documentation`, `enhancement:*`, `status: needs-info`, `Platform: MacOS`, and broader provider labels. That conflicts with the new package's native Issue Type model, `needs: info`, lowercase `platform:*`, and canonical label taxonomy. Existing morning/find-review/stale-verification docs also still mention release labels or priority labels in ways that conflict with the new policy.
- Recommendation: Update the active maintainer skills that apply or recommend metadata to load the new `nemoclaw-maintainer-policies` references, or explicitly mark the old embedded triage/reference files as superseded so agents cannot keep using both policy sources.
- Evidence: New `workflow-policy.md` says consumers must use this package for canonical write policy. Nearby existing files still reference legacy rules: `.agents/skills/nemoclaw-maintainer-triage/SKILL.md` reads its own `references/triage-instructions.md`; that legacy reference lists `bug`, `enhancement:*`, `documentation`, `status: needs-info`, `Platform: MacOS`, and provider labels not present in the new taxonomy.

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.

github-actions · 2026-06-05T18:59:39Z

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

None. No E2E is recommended. The PR only adds maintainer policy/skill documentation and changes GitHub issue-template metadata. It does not touch runtime source code, installer/onboarding logic, sandbox lifecycle, credential handling, security enforcement, network policies, inference routing, deployment, or real assistant user flows covered by E2E tests.

Optional E2E

None.

New E2E recommendations

None.

github-actions · 2026-06-05T18:59:40Z

E2E Scenario Advisor Recommendation

Required scenario E2E: None
Optional scenario E2E: None

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

None. Changes are limited to maintainer policy/agent skill documentation and GitHub issue templates. They do not modify test/e2e-scenario runtime, scenario metadata, expected-state contracts, suite definitions, scenario workflows, suite scripts, or onboarding/install helpers exercised by scenario E2E.

Optional scenario E2E

None.

Relevant changed files

None.

docs: add NemoClaw maintainer workflow policies

2fb351e

wscurran self-assigned this Jun 5, 2026

wscurran added v0.0.60 Release target area: skills Skills, agent behaviors, prompts, or skill packaging chore Build, CI, dependency, or tooling maintenance labels Jun 5, 2026

wscurran added 2 commits June 5, 2026 11:42

docs: resolve skills guide against main

dce274c

Merge latest main into maintainer policy PR

2f1b081

wscurran changed the title ~~Add agent-ready NemoClaw maintainer workflow policies~~ docs: add agent-ready NemoClaw maintainer workflow policies Jun 5, 2026

wscurran enabled auto-merge (squash) June 5, 2026 19:02

wscurran requested review from cv and miyoungc June 5, 2026 19:02

cv approved these changes Jun 5, 2026

View reviewed changes

cv disabled auto-merge June 5, 2026 19:26

cv merged commit 18be269 into main Jun 5, 2026
24 of 26 checks passed

cv deleted the codex/nemoclaw-community-governance branch June 5, 2026 19:26

This was referenced Jun 8, 2026

docs(policy): refine shared triage taxonomy #4935

Merged

chore(github): tighten bug report intake #4954

Merged

Conversation

wscurran commented Jun 5, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Validation

Summary by CodeRabbit

Uh oh!

copy-pr-bot Bot commented Jun 5, 2026

Uh oh!

coderabbitai Bot commented Jun 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Suggested labels

Suggested reviewers

Poem

Uh oh!

github-actions Bot commented Jun 5, 2026

PR Review Advisor

🛠️ Needs attention

🔎 Worth checking

🌱 Nice ideas

Uh oh!

github-actions Bot commented Jun 5, 2026

E2E Advisor Recommendation

E2E Recommendation Advisor

Required E2E

Optional E2E

New E2E recommendations

Uh oh!

github-actions Bot commented Jun 5, 2026

E2E Scenario Advisor Recommendation

E2E Scenario Advisor

Required scenario E2E

Optional scenario E2E

Relevant changed files

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

wscurran commented Jun 5, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jun 5, 2026 •

edited

Loading