Enforces flat hexagonal architecture and dependency direction for Go project layouts.
npx skills add https://github.com/trypanic/skills --skill go-modularization
Please help me install this Agent Skill. Skill: go-modularization Source: https://github.com/trypanic/skills/tree/main/go-modularization Command: npx skills add https://github.com/trypanic/skills --skill go-modularization
Go monorepos and single-service repositories often suffer from inconsistent folder layouts, layering violations, and ambiguous file placement that slow down development and review. This Skill eliminates that ambiguity by providing opinionated, deterministic rules for where every type of Go source file, adapter, migration, and shared package belongs.
Use the go-modularization skill to determine the correct destination folder and filename for a new Go source file in your service's internal directory.
High-intent search queries and answers about installing and using this skill.
You can enforce a consistent Go monorepo folder layout by applying a flat hexagonal architecture with strict dependency direction rules. This approach governs where source files, adapters, and shared packages belong across bounded contexts and service boundaries.
Organizing Go source files with hexagonal architecture involves separating inner layers like domain, interactor, ports, and coordinator from outer adapters such as api, consumer, cli, and data repositories. This enforces strict dependency direction between layers.
Validating Go project architecture rules in CI pipelines uses an arch-checks gate script to enforce module topology rules, promotion thresholds, and forbidden name validation. This prevents layering violations and ambiguous file placement from merging into the repository.
Yes, you can apply strict architecture rules to an existing brownfield Go codebase by following an incremental migration guide. This helps adopt folder layout conventions and dependency direction rules without requiring a complete rewrite.
You need to promote Go source files into subfolders based on promotion threshold counting rules. This governs when to move suffixed files into bounded contexts, API versions, middleware, or external provider directories to maintain code organization.
Go monorepos suffer from layering violations and ambiguous file placement when lacking deterministic rules for source file, adapter, and migration locations. Applying opinionated folder layout conventions and CI-gated architecture validation eliminates this ambiguity.
vlad-ryzhkovAudit Go backend repositories for API endpoints, infrastructure, and test coverage.
mytechsonamyEnforce architectural rule compliance for code changes during pre-merge reviews.
CsHengValidate Go code through compilation, linting, testing, and dependency checks.
bjorkgardDecompose monolithic code into modular DDD bounded contexts.
