Hi everyone,
I’ve been experimenting with some ways to simplify everyday coding tasks, and I ended up building a small CLI tool called Code-Genie. It’s open-source, and I thought it might be useful to share it here with the Forem community.
GitHub Repo: https://github.com/Sherin-SEF-AI/code-genie
🌱 Why I Built It
I found myself switching between the terminal, editor, browser, and docs for even the smallest code fixes. Most of these tasks didn’t require a full IDE session — just a quick solution.
So I made a simple tool that lets me:
- describe a change in plain English
- apply that change to a file
- generate small pieces of code when needed
- fix errors or refactor without context overload
Nothing fancy — just something that reduced friction for me.
✨ What Code-Genie Does
You can type things like:
codegenie "Refactor this to async/await"
or
codegenie "Fix the undefined variable"
or even:
codegenie "Create a FastAPI POST endpoint"
It reads your file, sends context to an LLM (configurable), and applies only the required changes.
🔧 How It Works
- Python CLI
- Supports OpenAI, Anthropic, Groq, or local models
- Minimal code diffing
- Designed to be easy to extend and hack on
I kept the codebase intentionally small so contributors can understand it easily.
📦 Installation
clone the repo:
git clone https://github.com/Sherin-SEF-AI/code-genie
🙏 Looking for Feedback & Suggestions
This is an early project, and I’d genuinely appreciate:
- feature ideas
- bug reports
- language support suggestions
- feedback on the UX
Even small comments help a lot.
đź’¬ Question for the Community
What’s one small coding task you wish your terminal could just “handle for you”?
I’d love to explore more ideas to make this tool genuinely helpful.
Top comments (1)
This is really cool! Love the minimal design philosophy—reducing context switching is such an underrated win for productivity.
I've been working on something similar but at a larger scale—building AI developer kits that handle not just code editing, but entire workflow automation (API integration, data pipelines, test generation). Your CLI approach is actually the perfect complement to what we're exploring.
One thing I'm curious about: how does Code-Genie handle multi-file refactoring? Like if you need to change a function signature across 5 files, does it traverse that context or do you keep it single-file focused?
Also, the way you describe reducing friction in the development loop aligns perfectly with what developers actually want. If you're open to it, I'd love to explore how tools like this could work together—your elegant CLI with broader automation.
Genuinely impressive execution on the MVP. Would definitely be interested in testing this out and potentially collaborating.