dynamo-ecosystem-reviewer

Reviews code changes for cross-platform, service, and thread-safety constraints across Dynamo repositories.

2.0k|679|Updated Feb 9, 2012
One-click install
npx skills add https://github.com/DynamoDS/Dynamo --skill dynamo-ecosystem-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dynamo-ecosystem-reviewer
Source: https://github.com/DynamoDS/Dynamo/tree/main/.claude/skills/dynamo-ecosystem-reviewer
Command: npx skills add https://github.com/DynamoDS/Dynamo --skill dynamo-ecosystem-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes in Dynamo can silently break when deployed across its ecosystem — running headless as a service, inside Revit's UI-thread scheduler, or across multiple related repos. This Skill catches ecosystem-level compatibility issues that single-repo reviews miss.

Core Features & Use Cases

  • Cross-Platform Compatibility Checks: Verifies that code added to Dynamo core runs headless without UI dependencies and works when Dynamo runs as a service.
  • Thread-Safety Analysis for Revit: Flags dispatcher calls, Invoke, and async patterns that assume a separate UI thread, which deadlock in Revit where the UI thread is the scheduler thread.
  • Multi-Repo Impact Review: Considers how changes ripple across Dynamo, DynamoRevit, DynamoSandbox, and other related repositories when shared APIs or contracts are touched.
  • Use Case: A developer submits a pull request to Dynamo core that adds a background task waiting on a dispatcher callback. The reviewer flags that this pattern deadlocks in the Revit context and names the specific constraint violated.

Quick Start

Review this pull request for compatibility with the broader Dynamo ecosystem, including headless service execution and Revit thread-safety constraints.

Frequently Asked Questions about dynamo-ecosystem-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Dynamo code for cross-platform compatibility?

Check that code added to Dynamo core runs headless with no UI dependencies and makes no assumptions about a desktop environment. The reviewer applies these constraints automatically based on which repo and layer the change targets.

Why does my Dynamo code deadlock when running inside Revit?

In Revit, the UI thread is the scheduler thread, so code that blocks waiting for the UI thread deadlocks. Dispatcher calls, Invoke, or async patterns assuming a separate UI thread are the usual cause and should be flagged during review.

Can Dynamo core code depend on UI components?

No. Dynamo core must run headless so it can operate as a service without a desktop environment. Any UI dependency introduced into core code violates this constraint and will break service deployments.

Which Dynamo repositories does an ecosystem review cover?

The review considers Dynamo, DynamoRevit, DynamoSandbox, and other related repos. When a change touches shared APIs or contracts, the reviewer looks across repositories to assess ripple effects.

When should I use ecosystem-level review instead of a standard code review?

Use it when changes touch Dynamo core, shared APIs, or contracts consumed by multiple repos. Standard reviews catch local logic errors, but ecosystem constraints like headless execution and Revit thread safety require platform-wide context.