refactor-architect

Analyze Go codebases and monorepos to generate structured refactor plans and modular specs.

8|3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ydnikolaev/antigravity-factory --skill refactor-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor-architect
Source: https://github.com/ydnikolaev/antigravity-factory/tree/main/src/skills/refactor-architect
Command: npx skills add https://github.com/ydnikolaev/antigravity-factory --skill refactor-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go1.25.

What problem does it solve?

Analyzes codebases to identify refactoring needs and reduces tech debt by outlining modular specs.

Core Features & Use Cases

  • Static analysis-first planning: runs a static analysis pass to surface high-impact refactors.
  • Context7-informed guidance: queries Context7 for best practices to shape architecture.
  • Enforcement artifacts: produces modular specs and enforcement rules for downstream executors.
  • Use Case: For a large Go monorepo, generates a refactor roadmap with domain modules and migration steps.

Quick Start

Run the analyzer on your repository to generate a refactor-overview and module specs.

Frequently Asked Questions about refactor-architect

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

FAQPage Schema
How do I plan a modular refactor for a large Go monorepo?

Plan a Go monorepo refactor by running static analysis to surface high-impact targets, querying Context7 for best practices, and generating a structured roadmap with domain modules and migration steps.

What is static analysis-first refactoring and when do I need it?

Static analysis-first refactoring identifies structural pain points and tech debt before code changes. It is needed when a Go codebase requires modular specs and governance artifacts to guide downstream executors safely.

How do I generate enforcement rules and domain-module specifications for my codebase?

Generate enforcement rules and domain-module specifications by analyzing the codebase structure, querying Context7 for architectural best practices, and producing governance artifacts for downstream execution.

Can I use this refactoring approach for non-Go projects or repositories?

This refactoring approach is specifically designed for Go projects and monorepos, requiring the go1.25 dependency. It is not applicable to non-Go codebases.

Does Context7 integration help enforce code quality during refactoring?

Context7 integration helps enforce code quality by querying best practices to shape the architecture, ensuring the generated modular specs and enforcement rules align with current standards.

What are the limitations of using static analysis for codebase refactoring?

Static analysis for refactoring outlines modular specs and governance artifacts but does not execute code changes itself. It requires downstream executors to apply the generated refactor plans to the Go codebase.