Guide for adding a new benchmark or training environment to NeMo-Gym. Use when the user asks to add, create, or integrate a benchmark, evaluation, training environment, or resources server into NeMo-Gym. Also use when wrapping an existing 3rd-party benchmark library. Covers the full workflow: data preparation…
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Use when designing a new benchenv task suite, adding several new tasks to an existing suite, or critiquing a task-set proposal for a mobile-gym App — before any class FooTask(...) is written under benchenv/task/.
Use when adding or modifying offline judge tests for benchenv tasks — specifically entries in OFFLINEJUDGEPOSITIVECASES / OFFLINEJUDGENEGATIVECASES in benchenv/tests/ /testtasks.py, or writing live tests. Triggers after a new task is added, or when tightening judge coverage.
Use when writing or modifying checkgoals() / getanswer() / App check methods in benchenv/task/, or when reviewing a draft task's judge correctness. Triggers include adding a new task, editing a judge method, or diagnosing a judge false-positive/negative.
Turn a gym's existing cameras and class schedule into attendance and trainer-performance analytics — daily summaries, per-trainer fill rates and no-shows, classes ranked by profitability. Use when a gym owner asks which classes to cut, who their best trainer is, how busy the gym is today, or which classes make money …