validate-codemod-recipe

To validate a codemod, you run it against a target directory to inspect diffs and iteratively fix AST transform issues like false positives and broken references, ensuring consistent codebase maintenance.

AST transform analysis inspects every diff produced by a migration recipe to identify issues such as false positives, redundant transforms, and broken references within the abstract syntax tree of a codebase.

You fix false positives and broken references in codemod output by running the recipe against a real codebase, inspecting the resulting diffs, and iteratively adjusting the AST transforms to correct the errors.

Yes, adding and updating test fixtures is necessary to ensure your codemod's correctness, as they provide controlled inputs for validating AST transforms and preventing build-breaking code changes.

Yes, you can automate iterative testing for codebase maintenance by running codemods against a real codebase, validating their output, and automatically fixing AST transform issues to reduce manual effort.

Running codemods against a target directory requires a valid codemod path and a real codebase to inspect diffs accurately; without proper test fixtures, iterative fixing of AST transforms may not prevent all build errors.