Audit Unity .asmdef assembly dependencies and generate Mermaid graphs and issue reports.
npx skills add https://github.com/tykisgod/quick-question --skill deps-tykisgod
Please help me install this Agent Skill. Skill: deps Source: https://github.com/tykisgod/quick-question/tree/main/skills/deps Command: npx skills add https://github.com/tykisgod/quick-question --skill deps-tykisgod
For Unity game development projects, manually tracking assembly (.asmdef) dependency relationships across dozens or hundreds of modules is extremely time-consuming and error-prone. Undetected circular dependencies and architecture layer violations often lead to obscure build failures, runtime crashes, and technical debt that is difficult to resolve as the project scales.
Use the deps skill to analyze all .asmdef dependency relationships in your current Unity project and output the full dependency health report with graphs, matrix, and issue flags.
High-intent search queries and answers about installing and using this skill.
Mapping Unity .asmdef dependencies and finding circular references is done by scanning assembly definition files to build a complete module dependency map. This process automatically flags circular dependencies and generates visual Mermaid graphs for reporting.
Visualizing .asmdef architecture layers is best achieved by generating a Mermaid flowchart and a dependency matrix. This visual reporting maps module relationships at a glance, making it simple to share architecture insights across your game development team.
Yes, detecting architecture layer violations in Unity .asmdef files can be fully automated using configurable inference logic. The system scans .asmdef reference relationships and automatically reports problematic dependency paths that violate your architecture layers.
Yes, .asmdef dependency analysis excludes Unity editor and test assemblies by default. When scanning all valid .asmdef files in your project to build the module dependency map, it filters out these assemblies to focus on core runtime architecture validation.
Obscure Unity build failures often happen because of undetected circular dependencies and architecture layer violations across module assemblies. Automatically auditing .asmdef dependency relationships detects these problematic paths to prevent intermittent build failures and runtime crashes.
devdavvScaffold Unity feature modules with folders, Assembly Definitions, and test assemblies.
thktGenerate architecture overview Markdown and Mermaid diagrams from codebase analysis.
coolbeevipConvert technical debt specifications into engineering issues with dependency tracking.
tapanshahAnalyze software architecture and generate Mermaid, PlantUML, or ASCII diagrams.
