hammer-dependency-analyzer

Diagnose SDL3 HammerEngine dependency health with circular dependency and layer violation reports.

14|2|Updated Mar 24, 2025
One-click install
npx skills add https://github.com/Ronin15/SDL3_HammerEngine_Template --skill hammer-dependency-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hammer-dependency-analyzer
Source: https://github.com/Ronin15/SDL3_HammerEngine_Template/tree/main/.claude/skills/hammer-dependency-analyzer
Command: npx skills add https://github.com/Ronin15/SDL3_HammerEngine_Template --skill hammer-dependency-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, git, bc, and includes scripts (resource) components.

What problem does it solve?

Complex C++ codebases often suffer from circular dependencies, tight coupling, and layer violations, leading to long compile times, fragile code, and architectural decay that is difficult to manage manually.

Core Features & Use Cases

  • Circular Dependency Detection: Identifies and suggests fixes for include cycles that break compilation, ensuring a clean and deterministic build process.
  • Layer Violation & Coupling Analysis: Enforces architectural rules (e.g., Managers don't depend on States) and quantifies coupling strength, highlighting areas for refactoring.
  • Header Bloat & Compile Time Impact: Pinpoints headers causing excessive recompilation and suggests forward declaration opportunities to significantly reduce build times.
  • Use Case: Before a major refactor, run a "Full Architecture Audit" to visualize the dependency graph, identify any new circular dependencies or layer violations, and get a health score for the codebase, ensuring architectural integrity.

Quick Start

Analyze dependencies for the entire HammerEngine codebase and check for circular dependencies.

Frequently Asked Questions about hammer-dependency-analyzer

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

FAQPage Schema
How do I detect circular dependencies in a C++ codebase?

Circular dependency detection identifies include cycles that break compilation by analyzing header relationships across your codebase. This tool scans C++ files to map dependencies, flag circular includes, and suggest fixes to ensure a clean, deterministic build process.

What's the best way to analyze coupling and layer violations in C++ architecture?

Layer violation and coupling analysis enforces architectural rules—such as preventing Managers from depending on States—and quantifies coupling strength across modules. This reveals refactoring opportunities and maintains clear separation between architectural layers.

How can I reduce C++ compile times by identifying header bloat?

Header bloat analysis pinpoints headers causing excessive recompilation and suggests forward declaration opportunities to eliminate unnecessary includes. Reducing header dependencies directly decreases build times and improves incremental compilation performance.

Can I use this tool to audit architecture before a major refactor?

Yes. A full architecture audit generates dependency graphs, identifies circular dependencies and layer violations, and produces a health score for your codebase. Run it before refactoring to establish a baseline and ensure architectural integrity throughout changes.

Does this work with existing C++ build systems and version control?

The tool integrates with git and standard C++ build environments, requiring python3, git, and bc. It works alongside your existing build system to generate coupling metrics, violation reports, and depth analyses without modifying your codebase.