skills.rest
Devattom
DevattomCOMMUNITY
Explore all skills by this author →
GitHub

architect

Detect architectural smells and refactor code with git history.

1|Updated Feb 26, 2026
Search Tags:#refactoring#git history#code architecture#module splitting#codebase audit#import management
One-click install
npx skills add https://github.com/Devattom/.claude --skill architect-devattom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Devattom/.claude/tree/main/skills/workflow-architect
Command: npx skills add https://github.com/Devattom/.claude --skill architect-devattom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill tackles complex codebase architecture issues, from identifying structural smells to safely refactoring code while preserving Git history and updating all imports.

Core Features & Use Cases

  • Codebase Auditing: Detects architectural smells like god modules, circular dependencies, and feature scatter.
  • Restructuring Plan: Proposes a safe, step-by-step plan for refactoring, including file moves and renames.
  • Safe Execution: Implements changes using git mv and automatically updates all imports.
  • Use Case: You need to reorganize a large, legacy codebase to improve maintainability. Use this Skill to audit the structure, get a plan for splitting large modules, and execute the refactoring without losing Git history.

Quick Start

Use the architect skill to restructure the 'src/components' directory.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I refactor a large codebase without losing git history?▼

To refactor a codebase without losing git history, use `git mv` to safely move and rename files. This preserves the commit history while updating the project structure and maintaining build integrity.

How do I detect architectural smells like circular dependencies in my code?▼

To detect architectural smells like circular dependencies, perform a codebase audit to analyze structure. This identifies god modules, circular dependencies, and feature scatter to highlight areas needing refactoring.

What is the best way to split god modules during a codebase restructuring?▼

The best way to split god modules is to first audit the codebase structure to detect them, then propose a safe, step-by-step restructuring plan. Execute the refactoring by moving files and updating imports.

Can I restructure a legacy codebase safely without breaking existing imports?▼

Yes, you can restructure a legacy codebase safely by executing changes with `git mv` and automatically updating all imports. This approach verifies build integrity and prevents breaking existing imports.

Why does feature scatter occur and how do I fix it during refactoring?▼

Feature scatter occurs when related code is spread across unrelated modules. A codebase audit detects this architectural smell, allowing you to propose a safe restructuring plan to consolidate features and update imports.

Related Skills

Explore More Software Engineering Skills→
flosrnflosrn

architect

Analyze codebase structure, detect architectural smells, and propose restructuring plans.

Community
Advanced
j-showj-show

review-helper

Review git diffs, apply fixes, and verify with pnpm check and test commands.

Official
Advanced
SpineEventEngineSpineEventEngine
2

move-files

Moves or renames git-tracked files and directories while preserving history and updating references.

Official
Advanced
jtucker9jtucker9

shard

Split monolithic source files into focused modules and update imports.

Community
Advanced