Development and Documentation Skills
Skills for working inside the Dynamo repository: investigation, proposals, review, and docs.
This page is for version v1.6.1.
For other versions, use one of these documentation indexes:
- Latest (v1.6.1) (default): https://docs.dynamo.nvidia.com/dynamo/latest/llms.txt
- dev: https://docs.dynamo.nvidia.com/dynamo/dev/llms.txt
- v1.6.1: https://docs.dynamo.nvidia.com/dynamo/v1.6.1/llms.txt
- v1.6.0: https://docs.dynamo.nvidia.com/dynamo/v1.6.0/llms.txt
- v1.5.1: https://docs.dynamo.nvidia.com/dynamo/v1.5.1/llms.txt
- v1.5.0: https://docs.dynamo.nvidia.com/dynamo/v1.5.0/llms.txt
- v1.4.2: https://docs.dynamo.nvidia.com/dynamo/v1.4.2/llms.txt
- v1.4.1: https://docs.dynamo.nvidia.com/dynamo/v1.4.1/llms.txt
- v1.4.0: https://docs.dynamo.nvidia.com/dynamo/v1.4.0/llms.txt
- v1.3.0: https://docs.dynamo.nvidia.com/dynamo/v1.3.0/llms.txt
- v1.2.1: https://docs.dynamo.nvidia.com/dynamo/v1.2.1/llms.txt
- v1.2.0: https://docs.dynamo.nvidia.com/dynamo/v1.2.0/llms.txt
- v1.1.1: https://docs.dynamo.nvidia.com/dynamo/v1.1.1/llms.txt
- v1.1.0: https://docs.dynamo.nvidia.com/dynamo/v1.1.0/llms.txt
- v1.0.2: https://docs.dynamo.nvidia.com/dynamo/v1.0.2/llms.txt
- v1.0.1: https://docs.dynamo.nvidia.com/dynamo/v1.0.1/llms.txt
- v1.0.0: https://docs.dynamo.nvidia.com/dynamo/v1.0.0/llms.txt
- v0.9.1: https://docs.dynamo.nvidia.com/dynamo/v-0-9-1/llms.txt
- v0.9.0: https://docs.dynamo.nvidia.com/dynamo/v-0-9-0/llms.txt
- v0.8.1: https://docs.dynamo.nvidia.com/dynamo/v-0-8-1/llms.txt
- v0.8.0: https://docs.dynamo.nvidia.com/dynamo/v-0-8-0/llms.txt
- v0.7.1: https://docs.dynamo.nvidia.com/dynamo/v-0-7-1/llms.txt
- v0.7.0: https://docs.dynamo.nvidia.com/dynamo/v-0-7-0/llms.txt
These skills operate on the repository itself: bug investigation, Dynamo Enhancement Proposals (DEPs), code review, continuous integration (CI) triage, and documentation authoring.
Prompts that reach them: “CI failed on my pull request. Tell me whether it is a real regression or a flake,” or “Draft a Dynamo Enhancement Proposal for the change I just described, then show it to me before filing.”
| Skill | Use for |
|---|---|
debug-session | Start a structured Dynamo bug investigation and maintain a persistent worklog. |
dep-create | Create or update a Dynamo Enhancement Proposal (DEP), implementation plan, or retroactive DEP. |
dep-status | Check DEP status, list DEPs by lifecycle or area, and find related proposals. |
dep-update | Triage a DEP, assign a person in charge, or advance its review and approval state. |
dynamo-agent-harness | Drive persistent Claude Code, Codex, or OpenCode sessions through a Dynamo endpoint over Agent Client Protocol (ACP). |
dynamo-clone-hotpath-audit | Audit Rust hot-path .clone() calls and, when requested, remove unnecessary clones. |
dynamo-docs | Add, update, move, or remove Dynamo docs, examples, recipes, and translations. |
dynamo-frontend-benchmark | Benchmark and profile the Dynamo frontend against mock workers. |
dynamo-kv-replay-parity | Validate byte parity and paired performance for offline KV-aware replay changes. |
fern-components | Select and use Fern MDX components when authoring or reviewing docs pages. |
fern-navigation | Design or change Fern navigation, tabs, sections, slugs, versions, and redirects. |
graham-code-review | Review Rust, systems, networking, or performance-critical changes with strict Dynamo standards. |
pr-monitor | Check pull request continuous integration (CI) health, diagnose failed jobs, distinguish regressions from flakes, and flag unexpected skips. |
repo-codeowners | Find who reviews a change, fix a failing codeowners check, or change review routing. |
visual-review | Build an interactive HTML code-review dashboard for a pull request, branch diff, or unified diff. |