metro-debugging

Debug Metro dependency injection errors in Kotlin Multiplatform projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/benoberkfell/claude-plugins --skill metro-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metro-debugging
Source: https://github.com/benoberkfell/claude-plugins/tree/main/plugins/metro/skills/metro-debugging
Command: npx skills add https://github.com/benoberkfell/claude-plugins --skill metro-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Metro dependency injection debugging helps developers identify and fix compile-time and runtime DI issues in Kotlin Multiplatform projects.

Core Features & Use Cases

  • Graph visualization and analysis for Metro-generated dependency graphs to pinpoint bottlenecks and misconfigurations.
  • Troubleshooting for missing bindings, dependency cycles, and scope mismatches across modules and platforms.
  • Runtime graph inspection and dynamic debugging workflows during development and CI to validate behavior.

Quick Start

Enable Metro diagnostics and generate a graph report for your project.

Frequently Asked Questions about metro-debugging

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

FAQPage Schema
How do I fix missing binding errors in Metro dependency injection for Kotlin Multiplatform?

Missing binding errors in Metro dependency injection are resolved by generating a graph report to pinpoint misconfigurations across modules, then applying actionable fixes for incomplete bindings in JVM and Android targets.

What is the best way to debug dependency cycles in Metro DI graphs?

Debugging dependency cycles in Metro DI graphs requires enabling Metro diagnostics to visualize the generated dependency graph. This visualization identifies bottlenecks and resolves circular dependencies across your Kotlin Multiplatform modules.

How do I enable Metro diagnostics to generate a dependency graph report?

You can enable Metro diagnostics by configuring your project Gradle configuration to output generated reports and graphs. This requires access to project build files to validate behavior and visualize dependency tasks during development.

Can I use Metro debugging workflows to inspect runtime graph bindings in Android targets?

Yes, Metro debugging supports runtime graph inspection and dynamic debugging workflows to validate behavior in Android targets. It works across compile-time graphs and runtime bindings to troubleshoot scope mismatches effectively.

Why does my Kotlin Multiplatform build fail with a Metro scope mismatch?

A Metro scope mismatch causes build failures when dependency scopes are inconsistent across modules in Kotlin Multiplatform projects. Enabling Metro diagnostics generates reports that identify scope mismatches and provide actionable fixes.

What are the limitations of troubleshooting Metro DI without graph visualization?

Without graph visualization, troubleshooting Metro DI is limited because you cannot easily identify dependency cycles, missing bindings, or scope mismatches across modules. Enabling Metro diagnostics generates visual graphs required for actionable fixes.