nemoclaw-maintainer-morning

Generate a daily release and triage plan for NemoClaw PRs and issues.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-maintainer-morning-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-morning
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NemoClaw/nemoclaw-maintainer-morning
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-maintainer-morning-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps NemoClaw maintainers start each workday with a clear, actionable shipping plan by triaging the backlog, selecting a target version, and quickly addressing stragglers from prior versions.

Core Features & Use Cases

  • Target version selection: Computes the next patch version and identifies items still labeled with older version targets so they can be handled first.
  • Backlog triage and ranking: Produces a prioritized queue for PRs and issues (optionally focusing on approved candidates) and enriches candidates with risky-area detection and a documented scoring model.
  • Operational labeling and daily plan output: Creates the version label, applies it to selected PRs/issues, saves the queue state, and outputs a daily plan including mix and readiness counts.

Quick Start

Run the Nemoclaw morning standup skill to triage the backlog, set the day’s version target labels, and generate the daily plan.

Frequently Asked Questions about nemoclaw-maintainer-morning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily release and triage plan for GitHub pull requests?

To generate a daily release and triage plan for GitHub pull requests, run the morning standup pipeline to compute the target patch version, surface backlog candidates, and apply version labels. This outputs a structured daily plan for prioritized shipping.

What is the best way to triage an issue backlog and prioritize PRs for a patch release?

Triage an issue backlog and prioritize PRs by executing a pipeline that ranks candidates using a documented scoring model and risky-area detection. This process identifies stragglers from prior versions and selects high-priority items for today's shipping scope.

How does version targeting work when managing GitHub pull requests and issues?

Version targeting for GitHub pull requests and issues works by determining the next patch version and identifying items labeled with older version targets. It creates a new version label, applies it to selected PRs and issues, and handles stragglers from previous releases first.

Can I merge high-priority security candidates into my daily GitHub triage queue?

Yes, you can merge high-priority security candidates into your daily GitHub triage queue. The morning planning pipeline optionally integrates these security candidates into the prioritized PR and issue queue alongside regular backlog items before generating the daily plan.

Does this triage and labeling workflow apply to NVIDIA NemoClaw repository maintenance?

Yes, this triage and labeling workflow applies to NVIDIA NemoClaw repository maintenance. It determines target patch versions, surfaces backlog candidates, and applies version labels directly to selected pull requests and issues within the NVIDIA NemoClaw project.

What is included in the structured daily plan output for morning maintainer standups?

The structured daily plan output for morning maintainer standups includes prioritized PR and issue selection, labeling decisions, and mix and readiness counts. It also saves the queue state to track the day's shipping scope and straggler handling progress.