r/codereview • u/It-Guy-2026 • 4h ago
True+True = 2 !!! 🤣
Started learning C++ and knew that in programming "true + true = 2" actually.
r/codereview • u/It-Guy-2026 • 4h ago
Started learning C++ and knew that in programming "true + true = 2" actually.
r/codereview • u/javinpaul • 4h ago
r/codereview • u/Bisuta3 • 5h ago
r/codereview • u/SquashHot4348 • 5h ago
You write a solution, hit Run, and see Accepted.
Great! 🎉
But have you ever stopped and wondered what actually happened between those lines of code?
I've often found myself wanting to see these things instead of just reading through the code or manually debugging every step.
So, I decided to build something around that idea.
It's a code visualizer + debugger built for people solving LeetCode problems.
The idea is simple: Don't just execute your code. Visualize how it works.
With AlgoLens, you can:
I've also tried to make it feel a little more interactive — almost like turning the debugging process into a game. 🎮
AlgoLens is currently available as a free Microsoft Edge extension:
👉 https://microsoftedge.microsoft.com/addons/detail/jhhkkpabkoeaiajdilomalbmjdppcmcc
Don't use Edge? No problem!
You can also use it on chrome -> Watch video for reference[ AlgoLens - chrome ]
I'm still developing and improving it, so I'd genuinely appreciate feedback.
One thing I'd love to know: What's the one thing you wish you could visualize while solving a LeetCode problem?
Would love to hear your thoughts! 🚀
r/codereview • u/Ok-Committee5924 • 8h ago
r/codereview • u/Ok-Committee5924 • 8h ago
r/codereview • u/SquashHot4348 • 14h ago
You write a solution, hit Run, and see Accepted.
Great! 🎉
But have you ever stopped and wondered what actually happened between those lines of code?
I've often found myself wanting to see these things instead of just reading through the code or manually debugging every step.
So, I decided to build something around that idea.
It's a code visualizer + debugger built for people solving LeetCode problems.
The idea is simple: Don't just execute your code. Visualize how it works.
With AlgoLens, you can:
I've also tried to make it feel a little more interactive — almost like turning the debugging process into a game. 🎮
AlgoLens is currently available as a free Microsoft Edge extension:
👉 https://microsoftedge.microsoft.com/addons/detail/jhhkkpabkoeaiajdilomalbmjdppcmcc
Don't use Edge? No problem!
You can also use it on chrome -> Watch video for reference[ AlgoLens - chrome ]
I'm still developing and improving it, so I'd genuinely appreciate feedback.
One thing I'd love to know: What's the one thing you wish you could visualize while solving a LeetCode problem?
Would love to hear your thoughts! 🚀
r/codereview • u/yellow-llama1 • 14h ago
Coding agents can modify code across multiple repositories, but reviewing the impact on dependencies and architecture is still difficult.
We've built an open-source tool, enola, that detects dependency cycles, layer violations, and structural regressions introduced by code changes.
It also lets agents track code symbols across refactors using enola locate, so stored references can be checked for changes.
In our benchmark, Claude Opus 5.5 answered 18/20 cross-repository architecture questions correctly with enola, compared with 4/20 without it.
GitHub: https://github.com/enola-labs/enola
It can run in the CI as an additional validation step.
How are you reviewing architectural impact when agents modify large codebases? How do you keep up with the increased velocity?
r/codereview • u/CH_CGV • 20h ago
r/codereview • u/No-Flight-7815 • 1d ago
Asking because i got burned and can't tell if my standards are broken or if everything out there is actually this mid.
We've had an AI code reviewer running on our repo for a few months. last week a migration locked writes on a 40m row table for six minutes and took checkout down - staging had 200 rows so nobody noticed, and sure enough the reviewer had said "no issues " on that PR. it literally cannot know the table is huge because it only reads the repo, it has no idea what's running in prod. so now i'm wondering what my bar even is.
I would at least expect that it backs its findings with evidence i can check ("this would exceed your table's lock budget at prod size") and says when it doesn't know something instead of green-checking. does that make sense?
r/codereview • u/Downtown-Warning6818 • 1d ago
r/codereview • u/Bisuta3 • 1d ago
r/codereview • u/Tatachimcooky • 2d ago
r/codereview • u/Ill-Government-1965 • 2d ago
While testing AI coding agents I kept seeing them suggest packages that were never published: express-rate-guard, react-auth-hooks-pro, reqeusts. That's a real risk, because attackers can register those exact names and wait for someone's agent to install them.
So I'm building ghostcheck Pro. Before anything installs, it checks for:
\- packages that don't exist on npm / PyPI
\- look-alike names (reqeusts → requests)
\- versions with known security advisories
\- secrets pasted into code
It runs locally (nothing is uploaded) and plugs into VS Code, Cursor, Claude Code, Codex and CI.
Waitlist (early price: $9 lifetime): https://ghostcheck-pro.vercel.app
I'd love honest feedback: would you trust a tool like this in your agent workflow, and what should it catch that I haven't listed?
r/codereview • u/No_Race7158 • 2d ago
Developer’s Eye is live. It’s an open-source search engine for developer docs and code examples. I built the crawler, indexer, and ranking system, and the hardest question so far has been a surprisingly ordinary one: when you search for a function, do you want its API reference or a working example?
Two trade-offs I ran into building it:
Want to contribute? The easiest way is to try the last thing you looked up while coding and reply with “I searched for ___ and expected ___.” A link to the page you wanted gives me a ranking test I can keep. If you’d rather write code, I’d love help adding a missing docs source or tracing why a specific result ranked too low. Drop the source or query in a GitHub issue and we can work on it together.
r/codereview • u/No_Race7158 • 2d ago
r/codereview • u/Ok_Abbreviations6960 • 3d ago
Are there any specific techniques or tools you use for this other than let claude review it? And how have you been approaching code reviews lately (the mindset/perspective)?
r/codereview • u/hibzy7 • 3d ago
r/codereview • u/CoolGuidance3352 • 3d ago
r/codereview • u/ishafiul • 3d ago
r/codereview • u/SquashHot4348 • 3d ago
Ever solved a LeetCode problem, got an Accepted, but still wondered what was actually happening inside your code?
I mean...
We usually understand the logic, write the code, and submit it. But sometimes, actually visualizing the execution is a completely different challenge.
I faced this quite often while solving DSA problems. Manually tracing every operation or using print statements wasn't always the most convenient way to understand what's happening.
So I started working on something to make this easier.
Meet AlgoLens!
It's a browser extension that lets you visualize how your code executes directly while solving LeetCode problems.
With AlgoLens, you can:
The idea is simple: instead of just reading your code and imagining its execution, actually watch it happen.
I've been building and improving this project, testing it across different LeetCode problems, and there's still a lot I'd love to add.
If you're curious to see it in action, here's the link:
🚀 AlgoLens: https://microsoftedge.microsoft.com/addons/detail/jhhkkpabkoeaiajdilomalbmjdppcmcc
I'd genuinely love to know:
If you could visualize one thing while solving DSA problems, what would it be?
Recursion trees? Array operations? Pointers? Call stacks? Something else?
Let me know! I'd love to hear your thoughts and suggestions. 🙂
r/codereview • u/Delicious-Resolve977 • 3d ago
Hey r/codereview!
Over the past few weeks, we've been building an open-source PR review bot in Python (AgentBlackBox: https://github.com/ATP0925/AgentBlackBox) and wanted to share some technical challenges we solved regarding PR diff mapping and zero retention:
GitHub immediately throws a 422 Unprocessable Entity if an automated bot attempts to post an inline comment on a line number that doesn't exist within the PR's unified diff hunks. To solve this:
line + side or hunk position).Instead of storing customer code in databases or persistent storage, diffs are parsed and processed strictly in-memory during the webhook task execution and discarded immediately after review comments & SARIF outputs are dispatched.
suggestion BlocksWhen the review engine detects bugs, AST security violations, or weakened test assertions, it computes a localized drop-in replacement snippet formatted into GitHub's one-click ```suggestion blocks.
Repo: https://github.com/ATP0925/AgentBlackBox
Would love to hear how other teams handle diff parsing edge cases (like binary files, renamed files with similarity index, and large multi-chunk diffs)!