codeprobe-architecture

Name: codeprobe-architecture
Availability: InStock
Author: Nishil

Detect architectural issues like layer violations and circular dependencies across codebases.

4|2|Updated Mar 28, 2026

Search Tags:#architecture #analysis #code-quality #dependency-graph #circular-dependencies #layer-violations #god-objects

Ready to run

npx skills add https://github.com/nishilbhave/codeprobe --skill codeprobe-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codeprobe-architecture
Source: https://github.com/nishilbhave/codeprobe/tree/main/skills/codeprobe-architecture
Command: npx skills add https://github.com/nishilbhave/codeprobe --skill codeprobe-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects architectural and structural weaknesses in a codebase, including layer violations, circular dependencies, god objects, anemic domain models, missing boundaries, and config issues, to improve maintainability and scalability.

Core Features & Use Cases

Layer violations detection: flags business logic in controllers, presentation logic in models, and data access in views.
Circular dependencies & god objects: identifies cycles and oversized files/classes that hinder refactoring.
Missing boundaries & directory structure checks: ensures domain separation and adherence to project structure conventions.
Severity-scored findings with actionable prompts for architectural improvements across multiple languages and stacks.
Use case: when evaluating a medium-to-large codebase, generate a prioritized report that guides architectural consolidation and module boundaries.

Quick Start

Run a full architecture audit on your codebase to generate actionable findings.

Frequently Asked Questions about codeprobe-architecture

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

FAQPage Schema

How do I detect circular dependencies and layer violations in my codebase?▼

Detect circular dependencies and layer violations by running a rule-based architectural audit that analyzes your codebase structure, producing severity-scored findings with actionable fix prompts to resolve coupling and organizational flaws.

What are god objects and anemic domain models in software architecture?▼

God objects are oversized files or classes that hinder refactoring, while anemic domain models lack business logic. Architectural analysis identifies these structural weaknesses to improve maintainability and scalability across multiple languages.

Can I analyze architectural issues in medium to large scale projects across multiple languages?▼

Yes, you can analyze architectural issues in medium to large scale projects across multiple languages. The audit detects missing boundaries, directory structure problems, and config issues to ensure domain separation and convention adherence.

How do I identify missing boundaries and directory structure issues in my project?▼

Identify missing boundaries and directory structure issues through architectural analysis that checks domain separation and project structure conventions, generating a prioritized report guiding module boundary consolidation.

What is the best way to generate a prioritized report for architectural consolidation?▼

Generate a prioritized report for architectural consolidation by running a full architecture audit that produces severity-scored findings with fix prompts, targeting layering problems and coupling that hinder codebase evolution.

Do I need a pre-loaded dependency graph to check for architectural issues?▼

No, a pre-loaded dependency graph is optional. The analysis supports standalone mode using references, applying rule-based detection to flag layer violations, god objects, and config problems without requiring external graph input.