CodeScene

Connect the legacy repo to CodeScene.

Filter the Hotspot map for 'High Churn' and 'Low Health'.

Identify the top 10 files causing the most friction.

Review the 'Virtual Code Review' for specific refactoring advice.

Run the 'Knowledge Distribution' analysis.

Identify 'Abandoned Code' or areas where the architect is the sole contributor.

Assign pair-programming tasks in those specific areas to transfer knowledge.

Track the 'Knowledge Map' until the risk score decreases.

Enable CodeScene PR integration.

Automated bot comments on PRs that decrease Code Health.

Gate the merge if health drops below a certain threshold.

Focus human review only on high-complexity logic changes.

Request read-only access to the target's Git history.

Run a 'System Health' report.

Quantify the 'Debt Interest' (time spent fixing bugs vs. features).

Estimate the cost of remediation based on hotspot density.

Define architectural components in CodeScene.

Analyze 'Team Coordination' metrics.

Identify components where 3+ teams are making frequent changes.

Reorganize teams or split components to reduce coordination overhead.

Use CodeScene to track 'Planned vs. Unplanned' work.

Show the correlation between low health and high bug fix rate.

Present a dashboard showing that refactoring Hotspot X will save Y hours/month.

Track the improvement in 'Development Velocity' post-refactoring.

Direct new hires to the 'Knowledge Map' to see who owns what.

Identify 'Low Complexity/High Health' areas for initial tasks.

Use the 'Code Biomarkers' to explain why certain files are written the way they are.

Monitor the new hire's 'Contribution Trend' to ensure steady growth.