nemoclaw-maintainer-morning

Triages the NemoClaw backlog, selects a daily version target, and labels GitHub PRs and issues.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-morning-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-morning
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-morning
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-morning-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the NemoClaw repository need a repeatable start-of-day routine to decide what ships today: ranking the open backlog, picking the next patch version, catching items that slipped from previous releases, and labeling the chosen work so the daily release flow can begin. ## Core Features & Use Cases - Version Targeting: Computes the next patch version from git tags and surfaces stragglers still carrying older version labels. - Backlog Triage: Ranks open PRs using Project 199 Priority, review state, CI status, and risky-area scoring, including urgent security PRs. - Labeling and Planning: Applies the target version label to confirmed PRs and issues via the GitHub CLI, saves the queue to state, and outputs a daily plan table. - Use Case: A maintainer starts the workday, runs the morning standup, reviews the ranked queue, confirms which items target v0.0.8, and receives a plan showing owners and next actions for each item. ## Quick Start Ask the agent to run the NemoClaw morning standup and produce today's daily plan with a target version.

Frequently Asked Questions about nemoclaw-maintainer-morning

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

FAQPage Schema
How do I triage open PRs for a daily release on GitHub?

Run the triage script, which fetches open PRs through the GitHub CLI, reads Project 199 Priority, and enriches candidates with review, CI, file, and risky-area data. It then applies a documented scoring model to produce a ranked queue for the day.

How do I label GitHub PRs and issues with a target release version?

Use the GitHub CLI to create the version label and apply it with gh pr edit and gh issue edit using --add-label. On a PR the label activates daily release work; on an issue it serves as tracking or needs-PR coordination only.

What are stragglers in a release triage workflow?

Stragglers are open items still carrying older version labels after a tag was cut. They indicate interrupted post-tag housekeeping or items that slipped across cycles, and they should be addressed first by relabeling them to today's target or deferring them.

Does the morning standup merge or release the selected PRs?

No. The morning skill only triages, labels, and plans; actual release inclusion requires the labeled PR to be merged before cutoff. Daytime execution of the queue is handled by the separate nemoclaw-maintainer-day skill.

What happens if the approved-only triage returns too few PRs?

Rerun the triage script without the --approved-only flag to widen the candidate pool. You can also use find-review-pr to surface security PRs whose Project Priority is Urgent or High and merge them into the candidates.