DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to refactor code across a whole repo from one plain-language request with Baize

Describe a code change in plain language and let Baize find and edit every matching file in the repository.

Who it is forA developer maintaining a Python project who needs the same change made in many files, such as swapping one HTTP library for another.

The problemFinding and editing every usage of a library by hand is slow and easy to get wrong.

The outcomeBaize searches the repo, edits the matching files, and reports what it changed.

What you need first

  • Python 3.10 or newer with pip
  • An API key for DeepSeek or another supported backend, or a local Ollama install
  • Optional: IBM SPSS Statistics or a reachable SQL database, depending on the use case

Steps

  1. pip install https://github.com/Xu123-Bob/Baize.git
  2. Open ~/.baize/config.toml, set active_provider to the backend you have a key for, and save your key in ~/.baize/.env. (inferred, check the README)
  3. Change into the repository you want to edit, then run baize. (inferred, check the README)
  4. At the >>> Decree: prompt, type: Find all places in this repository that use requests and change them to httpx
  5. Run your tests or a grep for the old library name to confirm the change.

Prompt for your agent

Using the Baize CLI from the Xu123-Bob/Baize repo, run the instruction 'Find all places in <repo-path> that use requests and change them to httpx' inside <repo-path>. Expected output: a list of edited files. Verify that no file in <repo-path> still imports requests.

Caveat. Baize needs a working LLM backend, so you must add an API key or run Ollama before the first decree works.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page