Skip to main content
deptrac-fixer Diagnose and fix Deptrac architectural violations automatically. Use when Deptrac reports dependency violations, layers are incorrectly coupled, or when refactoring code to respect hexagonal architecture boundaries. Never modifies deptrac.yaml - always fixes the code to match the architecture.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/VilnaCRM-Org/user-service --skill deptrac-fixerEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
Más de este repositorio Systematically retrieve and address PR code review comments using make pr-comments. Use when handling code review feedback or addressing PR comments.
Codex entrypoint for post-implementation BMAD FR/NFR review gates. Use after a PR, feature, or bugfix has BMAD specs and must be checked against every functional requirement, non-functional requirement, expanded quality dimension, Wikipedia system quality attribute, generated positive/negative/ edge test case, automated test and CI coverage expectation, flaky-test risk, whole-codebase impact surface, manual-test expectation, GitHub review comments and requested-changes state, and CI check before completion.
Run a BMAD spec-driven post-implementation review gate. Use after implementing a GitHub PR, feature, bugfix, or task with BMAD specs to verify every FR/NFR, pinned NonFunctionals.com NFR category, expanded quality dimension, Wikipedia system quality attribute, positive/negative/edge test case, automated test and CI coverage expectation, flaky-test risk, whole-codebase impact surface, manual test expectation, QA best practice, GitHub review comments and requested-changes state, and CI check before completion.
Explorador de archivos
8 archivos CODELY-STRUCTURE.md 17.2 KB name deptrac-fixer description Diagnose and fix Deptrac architectural violations automatically. Use when Deptrac reports dependency violations, layers are incorrectly coupled, or when refactoring code to respect hexagonal architecture boundaries. Never modifies deptrac.yaml - always fixes the code to match the architecture.
Deptrac Fixer Skill
Context (Input)
make deptrac reports violationsError message contains "must not depend on"
Domain layer has framework imports (Symfony, Doctrine, API Platform)
Infrastructure directly calls Application handlers
Any architectural boundary violation detected
Task (Function)
Diagnose and fix Deptrac violations by refactoring code to respect hexagonal architecture boundaries.
Success Criteria : make deptrac outputs "✅ No violations found"
Core Principle
Fix the code, NEVER modify deptrac.yaml
The architecture is correct. The code must conform to it, not vice versa.
Quick Start: Fix a Violation
Step 1: Run Deptrac
make deptrac
Step 2: Parse Violation Message
Domain must not depend on Symfony
src/Customer/Domain/Entity/Customer.php:8
uses Symfony\Component\Validator\Constraints as Assert
Extract:
Violating Layer : DomainForbidden Dependency : SymfonyFile & Line : src/Customer/Domain/Entity/Customer.php:8Violation Type : uses (import statement)
Step 3: Identify Fix Pattern
See : REFERENCE.md for complete fix patterns and advanced scenarios.
Step 4: Apply Fix Follow the pattern from examples, then verify:
Repeat until: "✅ No violations found"
Layer Dependency Rules Domain ─────────────────> (NO dependencies)
│
│
Application ──────────> Domain + Infrastructure + Symfony + API Platform
│
│
Infrastructure ───────> Domain + Application + Symfony + Doctrine
Layer Can Depend On Domain ❌ Nothing (pure PHP only) Application ✅ Domain, Infrastructure, Symfony, API Platform Infrastructure ✅ Domain, Application, Symfony, Doctrine ORM
Template examples use Doctrine ODM/MongoDB in places; apply the same patterns with Doctrine ORM and MySQL in this service.
Common Fix Patterns (Quick Reference)
Pattern 1: Domain → Symfony Validator ❌ Problem : Validation annotations in Domain entity
use Symfony \Component \Validator \Constraints as Assert ;
class Customer #[Assert\NotBlank ]
private string $name ;
}
✅ Solution : Move validation to config/validator/{Entity}.yaml
Pattern 2: Domain → Doctrine Annotations ❌ Problem : Doctrine attributes in Domain entity
use Doctrine \ODM \MongoDB \Mapping \Annotations as ODM ;
#[ODM \Document ]
class Customer ✅ Solution : Create XML mapping in config/doctrine/{Entity}.mongodb.xml
Pattern 3: Domain → API Platform ❌ Problem : API Platform attributes in Domain entity
use ApiPlatform \Metadata \ApiResource ;
#[ApiResource ]
class Customer ✅ Solution : Create YAML config in config/api_platform/resources/{entity}.yaml
Pattern 4: Infrastructure → Application Handler ❌ Problem : Direct handler call from Infrastructure
class Repository public function __construct (
private SomeHandler $handler // ❌ Circular dependency
) ✅ Solution : Use Command Bus pattern
class Repository public function __construct (
private CommandBusInterface $commandBus // ✅ Interface
) public function someMethod ($this ->commandBus->dispatch (new SomeCommand ());
}
}
See : examples/ directory for complete, runnable examples.
Diagnostic Workflow When facing multiple violations:
Step 1: Get All Violations make deptrac > violations.txt
Step 2: Categorize by Type Group violations by layer pair:
Domain → Symfony
Domain → Doctrine
Domain → API Platform
Infrastructure → Application
etc.
Step 3: Fix in Priority Order
Domain violations first (most critical)Infrastructure violations (circular dependencies)Application violations (least common)
Step 4: Verify Incrementally Track progress: 15 violations → 10 → 5 → 0 ✅
Constraints (Parameters)
NEVER
Modify deptrac.yaml to allow violations
Disable Deptrac checks
Add suppression comments or ignore directives (@SuppressWarnings, @psalm-suppress, @phpstan-ignore*, @infection-ignore*, phpcs:ignore)
Create "wrapper" classes to hide dependencies
Move entire class to wrong layer just to satisfy Deptrac
Move classes into unrelated/random directories just to make Deptrac pass (for example, hiding Generator classes under Factory)
Brute-force Deptrac by reorganizing code around tool output instead of business responsibility
Create ad-hoc directory/class types; use only well-known software patterns (e.g., Strategy, Factory, Provider, Resolver, CQRS Command/Handler)
Use reflection or dynamic loading to bypass checks
ALWAYS
Fix the code to match the architecture
Keep Domain layer pure (no framework imports)
Use interfaces for cross-layer dependencies
Move configuration to YAML/XML files
Keep "Directory X contains ONLY class type X" semantics
For new directories/classes, use explicit, well-known pattern names aligned with DDD/CQRS
Verify fixes with make deptrac after each change
Check that tests still pass after refactoring
Format (Output)
Expected Deptrac Output Deptrac
Checking dependencies...
✅ No violations found
Expected CI Output ✅ CI checks successfully passed!
Verification Checklist
Related Skills
Quick Commands
make deptrac
vendor/bin/deptrac analyze --report-uncovered
make deptrac && make ci
Reference Documentation For detailed patterns, examples, and troubleshooting:
REFERENCE.md CODELY-STRUCTURE.md examples/
01-domain-symfony-validation.php - Fixing Symfony validation violations02-domain-doctrine-annotations.php - Removing Doctrine imports03-domain-api-platform.php - Moving API Platform config04-infrastructure-handler.php - Using Command Bus pattern
Anti-Patterns to Avoid
❌ DON'T Modify deptrac.yaml
paths:
- { collector: layer_domain , exclude: '.*Annotation.*' }
❌ DON'T Create Wrapper Classes
class MyValidator private SymfonyValidator $validator ;
}
❌ DON'T Move Classes to Wrong Layer
✅ DO Fix the Root Cause
Extract validation to YAML
Move configuration to XML
Use interfaces and dependency inversion
Respect layer responsibilities
Success Criteria Summary
✅ Zero Deptrac violations
✅ Domain layer pure (no framework imports)
✅ All configuration externalized (YAML/XML)
✅ Proper use of Command Bus for cross-layer communication
✅ All tests passing
✅ CI pipeline green
