seam-finder

Safe codebase cut-points for refactoring are identified by analyzing a dependency graph to find seams based on observability, funnel, and read/write asymmetry. The analysis ranks these candidate seams with scores and evidence to ensure safe code modification.

A codebase seam is an optimal point in the code structure where you can safely modify or extend functionality without disrupting existing logic. Identifying seams through code graph analysis enhances overall refactorability and isolates changes.

You can analyze a dependency graph by running a targeted command with your modification goal. The tool evaluates the graph to recommend specific actions like extending, wrapping, or splitting seams based on detailed structural evidence.

Yes, seam identification requires a pre-existing code graph to function. The tool depends entirely on this structural representation to evaluate modification goals and generate a prioritized list of safe refactoring cut-points.

The best way to plan safe code modifications is by ranking candidate seams according to structural asymmetry and observability. This approach provides actionable recommendations for extending or splitting code while minimizing disruption to the existing codebase.