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 |
MERGE-GATE.md
View on GitHub# Merge Gate Workflow
Run the last maintainer check before approval. Never merge automatically.
## Gates
For the full priority list see [PR-REVIEW-PRIORITIES.md](PR-REVIEW-PRIORITIES.md). A PR is approval-ready only when **all** hard gates pass:
1. **CI green** — all required checks in `statusCheckRollup`.
2. **No conflicts** — `mergeStateStatus` clean.
3. **No major CodeRabbit** — ignore style nits; block on correctness/security bugs.
4. **Risky code tested** — see [RISKY-AREAS.md](RISKY-AREAS.md). Confirm tests exist (added or pre-existing).
## Step 1: Run the Gate Checker
```bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/check-gates.ts <pr-number>
```
This checks all 4 gates programmatically and returns structured JSON with `allPass` and per-gate `pass`/`details`.
## Step 2: Interpret Results
The script handles the deterministic checks. You handle judgment calls:
- **Missing required checks:** The script verifies that `checks`, `commit-lint`, and `dco-check` are present in the status rollup. If any are missing, **workflows have not been triggered** — this happens on fork PRs from first-time contributors that need "Approve and run" clicked in the Actions tab. Go to the PR's Checks tab, approve the workflows, wait for all checks to complete, then re-run the gate checker. **Never approve a PR with missing checks.**
- **Conflicts (DIRTY):** Do NOT approve — GitHub invalidates approvals when new commits are pushed. Salvage first (rebase), wait for CI, then re-run the gate checker. Follow [SALVAGE-PR.md](SALVAGE-PR.md).
- **CI failing but narrow:** Follow the salvage workflow in [SALVAGE-PR.md](SALVAGE-PR.md).
- **CI pending:** Wait and re-check. Do not approve while checks are still running.
- **CodeRabbit:** Script flags unresolved major/critical threads. Review the `snippet` to confirm it's a real issue vs style nit. If doubt, leave unapproved.
- **Tests:** If `riskyCodeTested.pass` is false, follow [TEST-GAPS.md](TEST-GAPS.md).
## Step 3: Approve or Report
**Approve only when:** `allPass` is true AND `mergeStateStatus` is not DIRTY. Approving a PR with conflicts is wasted effort — the rebase will invalidate the approval.
The correct sequence for a conflicted PR: **salvage (rebase) → CI green → approve → report ready for merge.**
**All pass + no conflicts:** Approve and summarize why.
**Any fail:**
| Gate | Status | What is needed |
|------|--------|----------------|
| CI | Failing | Fix flaky timeout test |
| Conflicts | DIRTY | Rebase onto main first — approval would be invalidated |
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: 196k | Updated | Claude CodeCodex | Verified | Install |