srgn-cli

Syntax-aware code refactoring uses tree-sitter queries to confine edits to valid code regions, ensuring transformations only apply to intended language structures. This prevents accidental modifications to strings or comments during repository-wide migrations.

The safest way to preview repository-wide code migrations is using a dry-run mode. This outputs the planned transformations without modifying files, allowing you to verify scope and regex accuracy before execution.

Yes, you can scope regex edits to specific code structures like imports and docstrings. Tree-sitter-based parsing and anchored-scope refinement confine deterministic edits to valid language regions for targeted cleanup and updates.

Tree-sitter scoping works with Python, Rust, Go, TypeScript, C#, HCL, and C for bulk code transformations. It applies language-aware scopes to confine regex-driven edits to valid syntax regions across diverse codebases.

You can control CI pipeline failures during code transformations using explicit failure controls like --fail-no-files, --fail-any, and --fail-none. These flags determine pipeline behavior when globbing matches unexpected results.

Regex-driven code transformations require precise tree-sitter scoping to avoid unintended edits, and complex transformations may need explicit scope controls and dry-run previews. Without anchored-scope refinement, regex alone cannot safely parse nested language syntax.