ripgrep-edit - Razor Coding Tool

ripgrep-edit enables razor coding by allowing LLM workflows to operate with razor-thin context, input and output.

How it works

• 🔍 Search using ripgrep with configurable context lines
• 📄 Present matches in a clean, linear, easy-to-read format
• ✏️ Edit all matched code snippets in a single temporary file
• 💾 Apply changes back to original files
• 🛠️ Works with any editor via shell command

Demo

Build

git clone https://gitlab.com/aarcange/ripgrep-edit.git
cd ripgrep-edit
cargo build --release

Options

• -e, --regexp <REGEXP>: Regex pattern to search for
• -E, --editor <EDITOR>: Editor command (e.g., vim, emacs)
• -C, --context <N>: Number of context lines
• -A, --after-context <N>: Lines of context to show after each match
• -B, --before-context <N>: Lines of context to show before each match
• --require-all-files: Require all files in ripgrep output to be present in the edited file
• --context-separator <SEPARATOR>: Separator string between snippets
• --filename-prefix <PREFIX>: Prefix for filename lines
• -S, --smart-case: Enable smart case search
• -i, --ignore-case: Ignore case distinctions
• -w, --word-regexp: Force pattern to match only whole words
• -U, --multiline: Enable multiline matching
• --multiline-dotall: Enable dotall mode for multiline matching
• --sort <SORT>: Sort results by path, modified, accessed, or created time
• --sortr <SORT>: Sort results in reverse order by path, modified, accessed, or created time
• --dump-on-error: Dump processed tempfile to stderr on error

Examples

rg-edit [OPTIONS] --regexp <REGEXP> --editor <EDITOR> [PATHS...]
rg-edit -e "function\s*\(" -E vim src/
rg-edit -e "function\s*\(" -E "emacsclient" -C 8 src/
rg-edit -E vim -U -e '(?s)^<<<<<<<+ .*?^>>>>>>>+ ' # resolve git conflicts

Why It Was Built

Large codebases challenge LLMs due to context limits. Traditional vibe coding tools require reading snippets of multiple large files through the LLM agentic workflow.

ripgrep-edit solves this by:

• 🔄 Linearizing code snippets from multiple files
• 📌 Preserving context around each match
• 🧠 Enabling precise edits via LLMs or editors
• 🔄 Reapplying changes to original files

ripgrep-edit lets the programmer define the exact context needed, presenting it in a structured, linear format optimized for the LLM's key-value input. The resulting gain in efficiency enables real-time visibility into what the LLM is generating — allowing to interrupt, refine input, adjust directives, and eliminate unnecessary context, computation, and cost.

The goal is to optimize the LLM's most demanding task — writing code — by minimizing perplexity and maximizing efficiency.

How to use

This works best with tools like gptel-rewrite, where extra context can be included for more complex refactorings.

To be effective, ripgrep-edit requires a well-crafted prompt:

You are a careful programmer. Rewrite cross-file snippets.
Rewrite everything exactly the same except: the required change.
Keep the filenames at the start of the files.
Keep the separators at the end of the snippets.
Do not delete the filenames and the separators.
Do not add markdown fences.
Do not ask clarification.

rg-edit.el

• Provides rg-edit, rg-edit-git, rg-edit-git-conflicts functions
• rg-edit-git C-c r
• rg-edit-git-conflicts C-u C-c r

(add-to-list 'load-path "~/.../ripgrep-edit/emacs/")
(use-package rg-edit
  :ensure nil
  :config
  (setq-default rg-edit-auto-mark-whole-buffer t)
  (setq-default rg-edit-executable "~/.../ripgrep-edit/target/release/rg-edit"))

Why Not wgrep?

• Emacs' wgrep offers similar functionality but relies on interactive edits, such as C-c C-d to delete a line, which are incompatible with the full rewrites required in LLM-driven workflows.

• Unlike wgrep, ripgrep-edit is editor-agnostic and LLM-agnostic: any editor can be used, making it ideal for diverse environments, or simply to avoid opening multiple files with vim.

License