Skip to content

composio-community/nemoclaw-composio / .agents/skills/nemoclaw-maintainer-day

nemoclaw-maintainer-day

Verified

Runs 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.

FileKindSize
HOTSPOTS.mdmarkdown1.4 KB
MERGE-GATE.mdmarkdown2.6 KB
PR-REVIEW-PRIORITIES.mdmarkdown3.1 KB
RISKY-AREAS.mdmarkdown756 B
SALVAGE-PR.mdmarkdown3.3 KB
SECURITY-SWEEP.mdmarkdown1.6 KB
SEQUENCE-WORK.mdmarkdown1.6 KB
SKILL.mdskill md3.7 KB
STATE-SCHEMA.mdmarkdown1.5 KB
TEST-GAPS.mdmarkdown2.2 KB
scripts/bump-stragglers.tsscript2.4 KB
scripts/check-gates.tsscript10.1 KB
scripts/handoff-summary.tsscript3.9 KB
scripts/hotspots.tsscript3.9 KB
scripts/shared.tsscript6.3 KB
scripts/state.tsscript7.7 KB
scripts/triage.tsscript16.0 KB
scripts/version-progress.tsscript2.2 KB
scripts/version-target.tsscript4.3 KB

SEQUENCE-WORK.md

View on GitHub
# Sequence Work Workflow

Turn a large problem into a short sequence of mergeable slices.

## Step 1: Read the Full Problem Surface

Read greedily: issue body and comments, linked issues, linked PRs with review comments and status, touched code/tests/docs, recent `main` changes if the area is active.

Do not sequence work from the title alone.

## Step 2: Identify What Is Moving

Inventory overlapping open PRs and recently merged changes. For each: blocker that must land first? Dependency to build on? Conflict to avoid? Noise?

## Step 3: Define Slices

Each slice should have: one core objective, short file list, explicit tests, merge dependency list, stop condition.

Prefer substrate-first sequencing:

1. Extract stable helper or type boundary
2. Add regression tests for current behavior
3. Land behavioral fix or refactor on top
4. Remove duplication afterward

## Step 4: Rank

Use repo priorities: (1) backlog reduction, (2) security, (3) test coverage, (4) hotspot cooling.

A slice that unblocks several PRs moves up. An elegant but non-urgent slice moves down.

## Step 5: Output

| Order | Slice | Why now | Depends on | Tests |
|-------|-------|---------|------------|-------|
| 1 | Extract timeout parsing from onboard | Enables safe tests, reduces conflicts | None | Unit tests for invalid env values |

Also include: outstanding blockers, which slices are safe for the maintainer loop, where human design decisions are needed.

## Notes

- Every slice maps to real files, tests, and merge behavior — not abstract architecture.
- Prefer small serially mergeable changes over one ambitious cleanup branch.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall