composio-community/nemoclaw-composio / .agents/skills/nemoclaw-maintainer-day
nemoclaw-maintainer-day
VerifiedRuns the daytime maintainer loop for NemoClaw, prioritizing items labeled with the current version target. Picks the highest-value item, executes the right workflow (merge gate, salvage, security sweep, test gaps, hotspot cooling, or sequencing), and reports progress. Use during the workday to land PRs and close issues. Designed for /loop (e.g. /loop 10m /nemoclaw-maintainer-day). Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.
| File | Kind | Size |
|---|---|---|
| HOTSPOTS.md | markdown | 1.4 KB |
| MERGE-GATE.md | markdown | 2.6 KB |
| PR-REVIEW-PRIORITIES.md | markdown | 3.1 KB |
| RISKY-AREAS.md | markdown | 756 B |
| SALVAGE-PR.md | markdown | 3.3 KB |
| SECURITY-SWEEP.md | markdown | 1.6 KB |
| SEQUENCE-WORK.md | markdown | 1.6 KB |
| SKILL.md | skill md | 3.7 KB |
| STATE-SCHEMA.md | markdown | 1.5 KB |
| TEST-GAPS.md | markdown | 2.2 KB |
| scripts/bump-stragglers.ts | script | 2.4 KB |
| scripts/check-gates.ts | script | 10.1 KB |
| scripts/handoff-summary.ts | script | 3.9 KB |
| scripts/hotspots.ts | script | 3.9 KB |
| scripts/shared.ts | script | 6.3 KB |
| scripts/state.ts | script | 7.7 KB |
| scripts/triage.ts | script | 16.0 KB |
| scripts/version-progress.ts | script | 2.2 KB |
| scripts/version-target.ts | script | 4.3 KB |
SALVAGE-PR.md
View on GitHub# Salvage PR Workflow
Take one near-mergeable PR and make the smallest safe change to unblock it.
**Default to maintainer salvage.** When a maintainer picks an item from the queue, the assumption is they're doing the work now — rebase, fix conflicts, add missing tests, push. Do not default to "ask the contributor and wait" because that blocks the daily cadence. Only defer to the contributor when the fix requires understanding intent that isn't clear from the diff.
## Step 1: Gather Context
```bash
gh pr view <number> --repo NVIDIA/NemoClaw \
--json number,title,url,body,baseRefName,headRefName,author,files,commits,comments,reviews,statusCheckRollup,mergeStateStatus,reviewDecision
gh pr diff <number> --repo NVIDIA/NemoClaw
```
Also read: maintainer and CodeRabbit comments, linked issues, recent `main` changes in touched files. Understand the PR's purpose before coding.
## Step 2: Assess Fit
**Maintainer does it now:** rebase and resolve conflicts, add missing tests for risky code, fix one or two failing checks, apply small correctness fixes from review, narrow gate cleanup.
**Defer to contributor only when:** the fix requires a design change the maintainer can't judge from the diff, contributor intent is ambiguous and the wrong guess would change semantics, or the PR spans multiple subsystems the maintainer isn't familiar with.
## Step 3: Check Out and Reproduce
```bash
gh pr checkout <number>
git fetch origin --prune
```
Reproduce locally. Run narrowest relevant commands first.
## Step 4: Review PR Scope Before Fixing
Before fixing, review **all** changed files in the PR — not just the ones causing failures. Flag any files that expand the PR's scope unnecessarily (config changes, unrelated refactors, tool settings). Revert those to `main` if they aren't needed for the feature to work.
## Step 5: Fix Narrowly
Smallest change that clears the blocker. No opportunistic reformatting.
If risky code is touched (see [RISKY-AREAS.md](RISKY-AREAS.md)), treat missing tests as part of the fix — follow [TEST-GAPS.md](TEST-GAPS.md) when needed.
## Step 6: Conflicts
Resolve only mechanical conflicts (import ordering, adjacent additions, branch drift). Stop and summarize if the conflict changes behavior.
## Step 7: Validate
```bash
npm test # root integration tests
cd nemoclaw && npm test # plugin tests
npm run typecheck:cli # CLI type check
make check # all linters
```
Use only commands matching the changed area.
## Step 8: Push
Push when: fix is small, improves mergeability, validation passed, you have push permission. Never force-push. If you cannot push, prepare a comment describing the fix.
**Fork PRs:** Most PRs come from contributor forks. Check where to push:
```bash
gh pr view <number> --repo NVIDIA/NemoClaw --json headRepositoryOwner,headRepository,headRefName,maintainerCanModify
```
If `maintainerCanModify` is true, push directly to the fork:
```bash
git push git@github.com:<owner>/<repo>.git <local-branch>:<headRefName>
```
Do **not** push to `origin` — that creates a separate branch on NVIDIA/NemoClaw that won't appear in the PR.
## Step 9: Route to Merge Gate
If PR looks ready, follow [MERGE-GATE.md](MERGE-GATE.md).
## Notes
- Goal is safe backlog reduction, not finishing the PR at any cost.
- Never hide unresolved reviewer concerns.
- Use full GitHub links.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |