r/codereview • • 11h ago

Curious to know how the community is handling code reviews.

2 Upvotes

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 • • 5h ago

Would anyone be interested in an open-source AI PR review agent?

Thumbnail reddit.com
0 Upvotes

r/codereview • • 12h ago

CodeInspectus 4.1.0: one-command setup and fewer false alarms for a local security scanner

Thumbnail
reddit.com
0 Upvotes

r/codereview • • 12h ago

javascript A leaderboard you can't fake: deterministic replay, sealed replays and a source check

Thumbnail
tendril.hokora.xyz
0 Upvotes

r/codereview • • 16h ago

Wanna see how your code thinks? šŸ¤”

1 Upvotes

Wanna see how your code thinks? šŸ¤”

Ever solved a LeetCode problem, got an Accepted, but still wondered what was actually happening inside your code?

I mean...

  • How are variables changing at every step?

  • What's happening when a recursive function calls itself?

  • How does the call stack grow and shrink?

  • Which line is executing at a particular moment?

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:

  • šŸ” Trace your code step by step.

  • šŸŽÆ See the currently executing line highlighted in the editor.

  • šŸ“Š Watch variables change during execution.

  • 🌳 Visualize function calls and call stack changes.

  • šŸ’» Work with Python, Java, C++, and JavaScript.

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 • • 17h ago

Reviewing PRs automatically: Built an in-memory diff analyzer with line-to-hunk position mapping & one-click suggestions in Python

0 Upvotes

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:

1. The GitHub 422 Problem in Automated PR Reviews

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:

  • We parse the raw unified diff into structured hunks.

  • Map the target source file line to the exact diff position (line + side or hunk position).

  • If a finding falls on an unchanged context line outside any hunk, our formatter falls back to batching it into the high-level Walkthrough comment rather than failing the review run.

2. Zero Retention in RAM

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.

3. One-Click suggestion Blocks

When 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)!


r/codereview • • 21h ago

AGY / CODEX

Thumbnail reddit.com
1 Upvotes

r/codereview • • 1d ago

Claude max for $29 instead of $200… how are these resellers even doing this?

0 Upvotes

r/codereview • • 2d ago

Spectre - A design-by-contract programming language with an explicit allocator-centric API that outperforms Zig by up to 6x on General Purpose Benchmarks

Thumbnail
github.com
2 Upvotes

r/codereview • • 2d ago

Functional Wanna see how your code thinks? šŸ¤”

Thumbnail
reddit.com
1 Upvotes

r/codereview • • 2d ago

LPT: Stop scrolling past generated code in PRs

0 Upvotes

When a codebase has generated files you have to commit, like protobuf stubs, mocks, GraphQL types or API clients, they show up in every PR.

You can make GitHub collapse them with a .gitattributes file committed in any folder:

*.pb.go               linguist-generated
**/__generated__/**   linguist-generated
mocks/**              linguist-generated

GitHub sometimes does this automatically for some files, but the default coverage is sparse.

I learned that many devs didn't know that the feature existed (while building my adjacent GH extension), and that's a loss in the age when reviews could take longer than the code itself.

NB: even generated files can still need a review, like db migrations when you still need to pay attention to these.

TL;DR Use .gitattributes!


r/codereview • • 2d ago

People to learn Gen AI with

2 Upvotes

Hey everyone! name is primeyy and i am learning GEN AI and since i have already build some decent rag project RAG and also fine-tuned a 4B model with custom dataset with complete project on Github now i wanna start with learning and building Agentic ai workflows with people who already have some experience with Gen ai or are really interested in learning together and, so if you are someone who is interested, just text me so that we can discuss about it. i have created a discord server for that so if you wanna join in just dm me here or send me a discord dm request on "0_o.prime"


r/codereview • • 3d ago

Made a small easy to use State Machine.

3 Upvotes

Wanted a state machine tool for myself in various projects but also for other developers, been having fun with it and learning more C# concepts.

Features

  • Enum-keyed states, using a non boxing key internally, the underlying value and the enum's type are packed into a struct, so no enum ever gets boxed

  • Nested substates, each with it's own events and it's own current substate

  • Predicate transitions that are safe to poll every frame (optional)

  • Optional context objects passed to handlers on enter, update and exit; sealed record types with value equality and built in deconstruction, up to 10 values

  • Per state Enabled flag and per substate update propagation

  • IndependentUpdate to tick a specific substate by a path of enum keys, mixing enum types freely across levels

  • Transitions requested from inside callbacks are queued and run after the current pass, so handlers can request transitions without breaking the machine

  • TryCreateState, TryGetState and StartState return false instead of throwing for common mistakes

Here's a quick use guide I made to demonstrate usage:

using SMachine;

public enum States { Idle, Combat }
public enum CombatSubs { Melee }

private string Name;
private int HeroAttack;

public void Initialize()
{
    var machine = new StateMachine();

    // States belong to the machine
    State idle = machine.CreateState(States.Idle);
    State combat = machine.CreateState(States.Combat);

    // Substates belong to a state
    SubState melee = combat.CreateState(CombatSubs.Melee);

    // Create a context object to pass to your handlers (optional)
    var ctx = new Context<string, int>("Hero", 10);

    // Subscribe to the events
    combat.OnEnter += () => Console.WriteLine("Combat has begun!");

    melee.OnEnterContext += (ctx) => {
        
        // I recommend using pattern matching for ease of use and safety
        if (ctx is Context<string, int>(string name, int attack))
        {
            Name = name;
            HeroAttack = attack;
        }
    };

    // Start your states
    machine.StartState(States.Combat); // This fires OnEnter
    combat.StartState(CombatSubs.Melee, ctx); // This fires OnEnterContext

    // Subscribe to the OnUpdateContext event
    melee.OnUpdateContext += HeroAttack;

    // Call Update on our machine for Combat state to update, then Melee
    machine.Update(ctx);
}

public void HeroAttack(BaseContext ctx)
{
    // We can also access context directly after casting
    var typed = (Context<string, int>)ctx;
    Console.WriteLine($"{typed.Data1} hits Goblin for {typed.Data2} damage!");
}

There are other features like Update Propagation, Independent Updates, and the Context type itself. I explain it all in detail over on my GitHub.

Let me know what you guys think, have any suggestions or just want to tell me I suck at programming (please don't be mean).


r/codereview • • 3d ago

Does it help code quality if agents encode their intents?

Thumbnail
rapidreview.dev
0 Upvotes

r/codereview • • 3d ago

Where do you run AI code review—locally before push, or on every PR update?

0 Upvotes

How are you fitting AI review into your Git workflow? Review locally after pulling the latest changes, trigger on PR creation, or re-run after every push? How do you avoid stale findings when the branch changes?

Disclosure: I’m affiliated with AxiomStudio.Ā VeraĀ reviews a specific PR revision on GitHub, GitLab, Bitbucket, or Azure Repos. Blockers become repair tickets; with fixes enabled, a coding agent updates the same PR and a fresh review checks the new revision.

For folks usingĀ CodeRabbit,Ā Bito, orĀ Cubic: do you let the reviewer block merges, or keep it advisory?

What’s your setup for handling new commits, failed CI checks, and false positives without adding more work?


r/codereview • • 3d ago

CALLING ALL DEVS- NEW TOOL

Post image
0 Upvotes

Introducing Rebel Verified, the newest developer platform from Rebel Tech Labs, Inc.

Here's why we built it.

Just because code runs, an AI agent marks a task complete, or a fix gets merged doesn't mean the underlying problem was actually resolved.

And frankly, I'm tired of seeing attempted execution confused with verified completion.

Don't just build it. Prove it.

Rebel Verified is designed to help developers, engineering teams, DevOps, and QA professionals identify gaps, diagnose issues, remediate with human approval, and verify that the work actually produced the intended outcome.

Detect → Diagnose → Remediate → Verify → Close the loop.

We're bringing verification into the development workflow with:

  • A free code scanner

  • CLI integration

  • GitHub Action

  • Human approval before remediation

  • Rescanning to verify fixes

  • Verification badges

Explore Rebel Verified:

https://rebeltechlabs.io/developers

This community is also a place to talk about what's working, what's broken, and what needs to change in how we build software.

So I'm curious:

What's the most frustrating example you've encountered of something being marked complete when it clearly wasn't?


r/codereview • • 3d ago

Python Looking for a volunteer code reviewer

Thumbnail
reddit.com
1 Upvotes

Looking for a volunteer code reviewer for an AI video automation project
I’m building an open-source Python project that automates parts of a faceless video production pipeline.
I’m looking for an experienced Python developer who could spare some time to independently review a GitHub pull request.
I’d especially appreciate feedback on:
Python architecture and reliability
GitHub Actions security
API keys and secret handling
Automated testing
Production readiness
Repository: https://github.com/anonalien420-cyber/faceless-creator
I’m bootstrapping this project and unfortunately cannot offer payment. I’m hoping someone in the developer community might be interested in helping an independent builder improve an open-source project.
Even a focused review of the security-sensitive changes would help enormously. Thank you.


r/codereview • • 4d ago

Java Need Help with a Simple Plugin!

Thumbnail reddit.com
1 Upvotes

r/codereview • • 4d ago

I'm from a non-IT background and have been learning Python. Would appreciate some honest feedback on my GitHub.

Thumbnail
reddit.com
2 Upvotes

r/codereview • • 3d ago

Do code reviews actually improve code quality, or do they sometimes slow everything down?

0 Upvotes

Code reviews are meant to catch mistakes and improve the quality of software, but sometimes they become little more than a formality. A quick approval without meaningful feedback doesĀ notĀ really help anyone improve.

On the other hand, a thoughtful review can help developers spot issues they might have missed and learn better approaches.

For developers here, have code reviews made a noticeable difference to your work, or do they sometimes feel like an unnecessary bottleneck?


r/codereview • • 4d ago

Why asking Claude Code to review its own diff in the same chat fails (+0.0 pp on LiveCodeBench) – built an open-source cross-CLI review gate (cold-jury)

0 Upvotes

If you ask the same coding agent session that just wrote a feature to review its own git diff, it almost always tells you the code looks great—even when it just introduced a subtle bug or refactored three unrelated files.

During the conversation, the model has already justified every decision in its context window. In the LiveCodeBench cross-model review study (arXiv:2607.21656: https://arxiv.org/abs/2607.21656):

  • Claude Sonnet 4 reviewing its own code: 91.4% -> 91.4% (+0.0 percentage points)

  • Claude Sonnet 4 reviewing OpenAI Codex drafts: 71.6% -> 89.7% (+18.1 percentage points)

  • GPT-4o-mini reviewing Claude Sonnet 4: 91.4% -> 94.0% (+2.6 percentage points)

To automate that cross-examination right before commit or git push, I built and open-sourced cold-jury (https://github.com/Dimoncelli/cold-jury, MIT, Node >=20, zero npm dependencies).

It applies Google's Elephant-Goldfish pattern: your main agent keeps the full project memory, while cold-jury spawns three ephemeral "goldfish" jurors in a different CLI (claude, codex, gemini, opencode, or local ollama) inside sterile temp directories with no chat history and a stripped environment allowlist:

  1. Pre-flight Secret Shield: scans the diff and --spec across 17 credential families (sk-ant-, sk_live_, AKIA, ghp_, PEM, JWT, DB URIs, .env) before spawning any subprocess. If it spots a P0 key, it blocks locally (exit 1) without sending anything out.

  2. 3 Parallel Hostile Probes: appsec (CWE vulnerabilities), correctness (logic bugs & race conditions), and surgical (YAGNI / scope creep against your --spec).

  3. Universal Skill & Git Hook: works standalone via npx, as a pre-push hook, or installed directly as a Skill (SKILL.md + .claude-plugin + agents/openai.yaml).

Quick commands to test it: npx --yes github:Dimoncelli/cold-jury doctor npx skills add Dimoncelli/cold-jury

Curious how others here structure their review step—do you spin up a fresh subagent, switch between Claude Code and Codex, or run automated pre-push gates?


r/codereview • • 4d ago

Half our review comments on AI-written PRs were things a script could have caught before the PR existed. So we made the script run first.

0 Upvotes

Reviewing code from a coding agent, the comments split into two piles. One pile needs a human: is this the right approach, does it handle the edge case, is the API shape sane. The other pile is mechanical: formatter not run, type check failing, a generated file edited by hand, a migration added without the matching down step, a lockfile out of sync. The second pile was bigger, and it was eating the review time the first pile needed.

The usual fix is CI, but CI runs after the PR is opened, so the mechanical comments still land in review, just from a bot. We wanted them to never reach the PR.

In CCode, the coding agent we build, hooks are scripts tied to moments in the agent's work, and the exit code decides what happens. The ones that moved review for us:

  • After every file edit, run the formatter and the type checker on that file. Failures go back to the agent as feedback, so it fixes them right then, while it still has the context.

  • Before a shell command runs, check it. Exit 2 blocks it and shows your message to the agent, so "don't edit generated files" or "no force-push" becomes a rule, not advice in a prompt.

  • When the agent says it's done, run the checks you'd run before opening a PR. Exit 2 sends it back to work.

What changed: the PRs that reach us pass the mechanical bar already, and review comments are the ones only a person can make. The agent also stops relearning your conventions from review feedback, because it hits them while working.

If you review AI-generated PRs: what share of your comments is mechanical, and have you managed to push any of it ahead of the PR?