toolkit-remix

Use when investigating RTX Remix Toolkit crashes, Kit minidumps, DXVK/HdRemix logs, Aftermath dumps, GPU device-lost failures, d3d9 crashes, capture-switch repros, or crash handoff bundles.

Use when investigating RTX Remix Toolkit crashes, Kit minidumps, DXVK/HdRemix logs, Aftermath dumps, GPU device-lost failures, d3d9 crashes, capture-switch repros, or crash handoff bundles.

Maintain multi-agent config: rules, commands, context, wrappers.

Run completion gates: tests, format, lint, changelog, docs, evidence.

Place/update docs: docs_dev developer, docs user-facing.

Extension docs/README.md structure: responsibilities, non-responsibilities, architecture.

Remove extension safely: deps, imports, app files, refs.

Add pip package to extension; OSRB/license/build steps.

Bump extension versions and write changelog entries for all modified extensions on this branch.

Create commit from staged/unstaged changes using repo git style.

Create and checkout a feature branch following the project's naming and base branch conventions.

Scaffold a new Omniverse Kit extension with the correct directory layout, config, premake, tests, and docs.

Diagnose extension load failures, missing test .bat files, import errors, or test discovery issues.

Run, filter, or troubleshoot Kit extension tests using the test .bat runner.

Promote durable learnings to repo docs/shared rules before done.

Run gates, push, create MR/PR.

Add a third-party pip package dependency to an extension, including OSRB license check and build integration.

How to maintain the multi-agent configuration — adding, editing, or syncing rules, commands, and context files across .agents/ and agent-specific wrappers.

Create a conventional commit from staged or unstaged changes, following the project's git workflow conventions.

Apply the repository's completion gates automatically before claiming work is done, including tests, format, lint, changelogs, version bumps, docs, and evidence reporting.

Guidelines for when and where to update documentation — docs_dev/ for developer docs, docs/ for user-facing content.

Required structure for extension docs/README.md — responsibilities, non-responsibilities, and architecture sections.

Promote stable project learnings into canonical repo docs or shared agent rules instead of leaving them only in private agent memory. Use before completing work or when new durable project knowledge is discovered.

Run all completion gates (format, lint, version bump, tests), push, and create a merge request or pull request.

Safely remove an extension — clean up all dependencies, imports, app files, and references across the repo.