srgn-clilisted

Build safe, syntax-aware srgn CLI commands for source-code search and transformation. Use for srgn commands, scoped refactors (comments/docstrings/imports/functions), multi-file rewrites with --glob, tree-sitter queries, or CI checks with --fail-any/--fail-none.
OutlineDriven/odin-claude-plugin · ★ 27 · AI & Automation · score 82

Install: claude install-skill OutlineDriven/odin-claude-plugin

# srgn CLI ## Overview Use this skill to convert user intent into precise `srgn` commands with safe defaults. Focus on CLI workflows for search, transformation, scoped migrations, and lint-like checks. ## Workflow Decision Tree 1. Classify the request. - Search only: no content changes expected. - Transform in stream: stdin/stdout pipeline usage. - Transform files: in-place updates over globs. 2. Identify scope strategy. - Regex scope only. - Language scope only. - Combined language + regex scope. - Custom tree-sitter query scope. 3. Identify action strategy. - Replacement (positional replacement argument after `--`). - Composable actions (`--upper`, `--lower`, `--titlecase`, `--normalize`, `--symbols`, `--german`). - Standalone actions (`-d`, `-s`). 4. Apply safety controls. - Prefer `--dry-run` for file operations. - Keep globs quoted. - Add `--fail-no-files` when missing files should fail CI. 5. Choose output mode. - Human-readable (default tty). - Machine-readable (`--stdout-detection force-pipe`). 6. Validate behavior. - Confirm expected match count. - Confirm no out-of-scope edits. - Re-run with stricter scope if needed. ## Safety Protocol 1. Default to non-destructive behavior first. - Prefer stdin-based or search-mode examples before in-place rewrites. 2. For file edits, require preview path. - Use `--dry-run` first. - Then run the same command without `--dry-run` only after confirmation. 3. Protect