codemods

Researches Backstage release breaking changes and drafts GitHub issues for backstage/codemods. Use when planning a Backstage version migration (e.g. 1.52.0), inventorying breaking changes for codemods, authoring codemod issue specs, deciding codemod vs document-only, or preparing migration issues before implementation. Also use when asked to parse release changelogs, cross-check upgrade notes, classify deprecations, or write Detection Criteria / Transformation Logic for a codemod issue. Does not implement codemods — hand off to the `codemod` skill after issues are filed.

Validate a codemod or migration recipe by running it against a real codebase and iteratively fixing issues found in the output. Use when asked to "test a codemod", "validate a recipe", "run the migration recipe and fix issues", "QA the codemods", "check the codemod output", or "clean up false positives". Also use when a codemod produces incorrect diffs, modifies files it shouldn't, leaves TODO comments that could be resolved, or breaks compilation in the target. Requires a codemod path and a target directory.