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

TEST-GAPS.md

View on GitHub
# Test Gaps Workflow

Close the highest-value test gaps without turning the task into a rewrite.

For risky code areas, see [RISKY-AREAS.md](RISKY-AREAS.md).

## Step 1: Collect File Set

Sources: files changed in target PR, recent failing CI, `main` churn in hotspot area, hotspot list in state file. If unknown, derive from highest-ranked actionable PRs.

## Step 2: Map to Existing Tests

Repo conventions:

- Root integration tests (`test/`): ESM imports
- Plugin tests: co-located as `*.test.ts`
- Shell logic: may need extraction into testable helper first

For each risky file: is there a test covering the changed behavior? Is it too indirect or flaky? Can a small extraction improve testability?

## Step 3: Choose Highest-Value Tests

Prefer tests that catch regressions the maintainer loop actually sees:

- invalid/boundary env values, shell quoting, retry/timeout behavior
- missing/malformed config, denied network/policy paths
- duplicate workflow/hook behavior, version/tag/DCO edge cases
- unauthorized or unsafe inputs

Include at least one negative-path test for risky code.

## Step 4: Extract Narrow Seams If Needed

Smallest extraction that improves testability: move parsing into a pure helper, separate construction from execution, factor hook logic into a reusable function, replace bags of primitives with typed helpers.

Do not broad-refactor under the label of "adding tests."

## Step 5: Add Tests

- CLI tests → `test/`
- Plugin tests → `nemoclaw/src/`
- TypeScript helpers → TypeScript tests
- Mock external systems; no real API calls in unit tests
- Security paths: prove the unsafe action is denied, not just that happy path works

## Step 6: Validate

```bash
npm test                          # root tests
cd nemoclaw && npm test           # plugin tests
npm run typecheck:cli
make check
```

Narrowest command set that gives confidence.

## Step 7: Report Gaps Honestly

If untested risk remains, say so: no clean seam without larger refactor, too much hidden shell state, missing fixture strategy, flaky infra dependency.

## Notes

- Tests for risky code are merge readiness, not polish.
- One precise regression test beats many vague integration checks.
- If credible fix needs bigger redesign, follow [SEQUENCE-WORK.md](SEQUENCE-WORK.md).
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: 194kUpdated Claude CodeCodexVerifiedInstall