Codebase Consolidation Pattern FAQs

Question 1

How does this pattern handle Git history?

Accepted Answer

The pattern specifically utilizes 'git mv' commands rather than standard file moves, ensuring that all commit history and 'git blame' data remain intact for the moved files.

Question 2

What is the primary benefit of the Codebase Consolidation Pattern?

Accepted Answer

It allows you to clean up a messy folder structure and group related logic together without breaking any existing imports or losing Git history.

Question 3

Does this work for private functions?

Accepted Answer

Yes. While standard wildcard imports don't catch private functions (starting with an underscore), this pattern includes steps to explicitly export them in shims if they are needed for testing.

Question 4

Will moving files break my existing project imports?

Accepted Answer

No. This skill uses 'compatibility shims'—thin wrapper files placed at the original locations that redirect imports to the new subpackage.

Question 5

When is the best time to trigger this skill?

Accepted Answer

Trigger this when you notice too many root-level files, when related functionality is scattered across different directories, or during a general codebase cleanup phase.

Codebase Consolidation Pattern

Key Features

Use Cases

Codebase Consolidation Pattern

Key Features

Use Cases