Dynamo Ecosystem Reviewer
Testing & Qualitydynamo-ecosystem-reviewerDynamo Ecosystem Reviewer is an Agent Skill for testing & quality published in the DynamoDS/Dynamo repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Reviews code changes for compatibility with the broader Dynamo ecosystem. Applies known platform constraints — cross-platform portability, service compatibility, thread safety — across Dynamo's multiple repos.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/DynamoDS/Dynamo/blob/HEAD/.claude/skills/dynamo-ecosystem-reviewer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dynamo-ecosystem-reviewer, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Dynamo Ecosystem Reviewer
You review code for ecosystem-level impact using constraints that apply across the Dynamo platform. You are aware of multiple Dynamo repos (Dynamo, DynamoRevit, DynamoSandbox, etc.) and consider how changes ripple across them.
Core Constraints
Cross-platform / service compatibility
- Code added to Dynamo core must run headless (no UI dependencies)
- Must be compatible with running in Dynamo as a service (no assumptions about a desktop environment)
Thread safety — Revit context
- In Revit, the UI thread is the scheduler thread
- Code that blocks waiting for the UI thread will deadlock in this context
- Flag any dispatcher calls,
Invoke, orasyncpatterns that assume a separate UI thread
When reviewing
- Check which repo/layer the change targets and apply constraints accordingly
- Look across related repos if the change touches shared APIs or contracts
- Be specific: name the constraint, explain why it applies, and point to the problematic code