CLI Toolkit

Install the CLI tools the cli-tools skills depend on (rg, fd, fzf, jq, jc, yq, rga, hyperfine) on Windows. Run once after installing the plugin.

Search and rewrite code by its syntax tree (AST), not plain text, using `ast-grep`. Use this skill when a text search would be too noisy or too blunt — finding a specific call shape, all usages of a pattern regardless of formatting/whitespace, structural lint rules, or performing a safe structural refactor with metavariables. Complements rg-fzf-dotnet: rg matches characters, ast-grep matches code structure. Supports C#, JS/TS, Python, Go, Rust, Java, and more. Install: winget ast-grep.ast-grep (binary: `ast-grep`, alias `sg`).

View file contents with syntax highlighting, line numbers, and git-change markers using `bat` — a `cat` replacement. Use this skill when reading a file or a specific line range for precise `path:line` references, when showing a snippet with highlighting, when using bat as an fzf/preview backend, or when you'd reach for `cat`/`head`/`tail` but want language-aware output. Always run non-interactively (`-pp` / `--paging=never`) inside an agent so it never blocks on a pager. Install: winget sharkdp.bat.

Multi-tool CLI pipelines for token-efficient agentic work — combining fd, rg, fzf, jc, jq, yq, gron, bat, sd, and ast-grep into cross-tool workflows. Use this skill when combining two or more CLI tools (fd+rg, rg+jc+jq, rg+fzf, yq+jq, gron+rg, rg+sd, ast-grep+jq), when output is too large and needs bounding, when deciding which pipeline to use for a task, when quoting rules differ between Git Bash / pwsh / cmd.exe, or when preparing an agent handoff paste.

Find files and directories by name, extension, path pattern, or type using `fd` — the fast, user-friendly alternative to `find`. Use this skill whenever the task is to locate files (not their contents): "find all .cs files", "where is the appsettings file?", "list all csproj files under BMS.NET", "find files matching *Controller*", "locate the Dockerfile". Prefer fd over rg --files for pure file-discovery tasks — it is faster, supports richer filters (type, depth, extension, owner), and produces cleaner output. Use rg-fzf-dotnet instead when you need to search file *contents* for symbols, text, or patterns.

Make JSON greppable by flattening it into discrete `path = value;` assignments, then reverse the transform with `gron -u`. Use this skill whenever JSON is too nested to query by eye, when you want to grep/rg for a key or value and see its full path, when jq's path syntax is unknown or awkward, or when diffing two JSON documents line-by-line. Pairs with rg (search the flattened lines) and jq (reshape afterwards). Install: winget TomHudson.gron.