← Use casesProduct & engineering

Codebase understanding & migration

Understand an existing repository and its dependencies, plan a migration, make changes under test coverage, and prepare a reversible release.

What to prepare

Inputs

Repository code, architecture notes, tests, migration goals, and compatibility requirements.

What to produce

Dependency and impact lists, migration code, test results, and release or rollback steps.

Break the work into verifiable stages, then choose models and supporting tools.

01
Map the repository
Locate entry points, configuration, data flows, and tests, then identify modules relevant to the goal.
02
Analyze migration risks
Check APIs, data formats, dependency versions, and external calls to determine verification order.
03
Implement and test incrementally
Change code in small batches, run relevant tests and real paths, and keep a diff record.
04
Prepare release and rollback
Define migration order, release checks, and rollback criteria, then confirm runtime behavior.

Combine models for the actual stages. The directory includes candidates matching one or more of these capabilities.

Code searchTerminal & test environmentVersion control & deployment tools

Compare cross-file understanding, tool use, and sustained execution.
A large context window does not automatically read a repository; retrieval and tool access need configuration.
Migration completion requires runtime and compatibility verification.

Read the codebase, map dependencies, implement migration changes, test compatibility, and document release and rollback steps.