jelly-bulk-edit

Bulk code refactoring uses AST-based pattern matching to transform code semantically across your entire codebase. This Skill applies ast-grep patterns to replace common patterns like console.log with logger, require to ES6 imports, var to const/let, and == to === while preserving code correctness and enabling preview before committing changes.

Yes. AST-based transformations work on both JavaScript and TypeScript projects, enabling safe pattern-based code changes across your repository. You define patterns using ast-grep syntax and apply them to targeted files or repo-wide, with interactive modes to review changes before execution.

The best approach is semantic pattern matching with AST tools, which understands code structure rather than text. This ensures replacements respect scope and context—replacing only the patterns you intend—while supporting preview and interactive application modes to keep changes reviewable and scoped.

AST-based transformation understands code structure and semantics, so it matches patterns contextually and preserves code meaning. Text-based find-and-replace can produce false matches and break syntax, while AST matching ensures only valid, intentional transformations occur across your codebase.

No. This Skill uses predefined pattern recipes for common migrations like require-to-import and var-to-const, eliminating the need for custom scripts. You define the pattern and target scope, then apply it interactively with built-in preview and validation to ensure correctness.

Transformations are scoped to files and patterns you explicitly define, so edge cases in dynamic code or complex metaprogramming may not be captured. Always preview changes and run tests after applying bulk transformations to catch unintended side effects in your specific codebase.