Analyze Go monorepo cohesion gaps and generate an executable restructuring plan.
npx skills add https://github.com/kaptinlin/gozod --skill code-restructuring
Please help me install this Agent Skill. Skill: code-restructuring Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/code-restructuring Command: npx skills add https://github.com/kaptinlin/gozod --skill code-restructuring
Full-repository architecture review and package reorganization to improve global cohesion, identify cohesion gaps, eliminate structural redundancy, restore cross-package cohesion, and generate an executable restructuring plan with import-cycle risk analysis.
Initiate the global-repository cohesion audit to generate an executable restructuring plan.
High-intent search queries and answers about installing and using this skill.
Large-scale Go monorepo refactoring requires a full-repository architecture review to identify cohesion gaps and generate an executable restructuring plan. This approach ensures planned migrations preserve behavior and provide rollback guidance through phased package reorganization.
Resolving import cycles during Go package reorganization requires an import-cycle risk analysis to detect structural dependencies. This generates a batchable restructuring plan that reorganizes packages by domain concern while eliminating circular references across multiple modules.
A global audit of Go packages for architecture cohesion evaluates all repository packages to identify boundary clarity issues and structural redundancy. It produces evidence-based recommendations for domain-driven reorganization to restore cross-package cohesion.
Yes, you can batch-execute repository restructuring plans for Go monorepos using a phased package reorganization strategy. This includes rollback guidance, risk analysis, and validation steps to ensure behavior preservation throughout the migration.
Global repo restructuring is necessary when a full-repository architecture review reveals widespread cohesion gaps and structural redundancy across multiple modules. Incremental refactoring cannot address cross-package import-cycle risks or provide batchable domain-driven reorganization at scale.
This restructuring approach provides domain-driven reorganization guidance, grouping Go packages by domain concern rather than artifact type. This method improves global cohesion and boundary clarity across the entire repository architecture.
rondevzStandardize Go project package naming, import organization, and dependency management.
codewithmukeshGenerate EF Core migration workflows with idempotent SQL and rollback plans.
cdman28Analyze Python and JavaScript/TypeScript code for smells, complexity, and refactoring opportunities.
dapperdiversRefactor Go codebases by moving code, renaming symbols, and restructuring packages with validation.
