type-collision-detector

What problem does it solve?

Accidental duplicate type names across different namespaces lead to ambiguous reference errors and messy codebases. This skill proactively identifies such collisions within your solution, suggesting clear naming conventions to prevent future compilation issues.

Core Features & Use Cases

• Solution-Wide Scan: Detects identical type names (e.g., Product in Domain.Models and API.DTOs) across all projects in your solution.
• Location & Context: Provides the file path, line number, and namespace for each colliding type.
• Intelligent Suggestions: Offers concrete renaming suggestions (e.g., ProductDto) to resolve conflicts.
• Use Case: Before creating a new Result class, you want to ensure it won't clash with existing types. Use type-collision-detector to check for any duplicates and get recommendations for a unique name.

Quick Start

Use the type-collision-detector skill to scan the entire solution for any duplicate type names.