How the Claude Code team does code review

(claude.dev)

55 points | by pretext 1 hour ago

15 comments

  • dylanhouli 39 minutes ago
    Here I am still unable to stop myself from doing line-by-line code review. I notice too many things (redundant code, duplicate code, overly complex architecture, etc.) by doing it that I feel it would be careless not to.
    • stillpointlab 14 minutes ago
      My advice is to start a totally vibe coded side project. You will never gain confidence until you experiment, find the failure cases, learn to deal with them, etc.

      Choose something you want to do but don't really care that much about. Be more ambitious than you think you could be, have a high bar on the outcome but purposefully choose to completely ignore the actual code. Make it write tests, dashboards, monitoring - whatever you need other than code to feel confident.

      Now is the cheapest time it will ever be to experiment.

    • benoau 36 minutes ago
      This is why I like GitHub Copilot's autocompletion, I'm right there guiding and policing the code as it appears.
    • dyauspitr 26 minutes ago
      No one cares about good code. It’s a means to an end. Your code doesn’t need to look pretty or be well documented or any of that stuff anymore because people are not looking at it. The only thing people care about is performant and error free code.
      • tripleee 21 minutes ago
        People saying this are telling on themselves that they have no idea what quality code is. It's not about looking pretty or nice variable names.

        Code quality matters to AI just as much as it did to people

        • bbctr1 20 minutes ago
          Do you have any data backing this statement? Or is it just your experience?
          • tripleee 18 minutes ago
            Simple example: code duplication all over the place, something AI loves to do. Update one of those without the others and you now have a bug.
      • gwynforthewyn 19 minutes ago
        Literally 50 years of engineering history and culture cares about whether code is good. There are libraries worth of books about it, not as a means to an app but for its own beauty. Just read “The Elements of Programming Style”, for example.

        Do what you want, write apps with AI and don’t review code, it doesn’t impact me. The claim that no one cares about good code is demonstrably false, and that’s all I’m objecting to.

        • g-b-r 17 minutes ago
          > it doesn’t impact me

          so long as his software isn't used for anything that can affect you

      • nerdo 20 minutes ago
        Not true, LLM’s will struggle with badly organized and designed large codebases just the same, though likely with less errors and profanities.
        • copperx 16 minutes ago
          The biggest concern is that AI can doxx you and find where you live if your code sucks. If that doesn't scare you, nothing will.
      • drewg123 3 minutes ago
        The way you phrase it makes me realize its almost like a GPL contamination. Eg, once you pull in GPL code, your project is infected and can never use a BSD (or other GPL incompatible) license.

        Similarly, once you pull in terrible AI slop code, the project becomes unmaintainable by humans and you need to maintain it with AI.

      • g-b-r 23 minutes ago
        Good code is a means to the end of the code being error (and vulnerability) free, maintainable and performant.

        And if people are not looking it, those people don't care about their customers.

    • g-b-r 37 minutes ago
      You're unable to stop being responsible? Tragic!
  • rileymichael 5 minutes ago
    what are people using for automated code review these days? the claude code review product originally mentioned it cost "$15-25 per review" (which is absurd), but it seems like they've removed that from their docs with the launch yesterday. we've looked at various products in the space (coderabbit, greptile, etc.) but have gripes with each.

    honestly i'm thinking it might be easier (and cheaper) to launch our own agent from GH webhooks and trigger `/code-review`..

  • vavkamil 42 minutes ago
    > Security gets its own automated review too. ... You either fix it or close the thread with a short reason, which is how you clear a false positive.

    I hope this is only for low-risk false positives. Dismissing a critical finding as a false positive should still involve AppSec.

    You could improve revert rates while simultaneously introducing more security vulnerabilities.

    And the linked "claude-code-security-review" explicitly states in the README

    > This action is not hardened against prompt injection attacks

    That's a significant limitation for an AI security review control, no?

  • hyperpape 42 minutes ago
    I'm somewhat surprised they would say Claude is writing 90% of their code at this point. Did they get tired of reporting new milestones, or has there been a plateau?
  • thisisauserid 39 minutes ago
    Remind me to invest more in the clouds they are burning those tokens in.
  • gonzalohm 38 minutes ago
    That explains why the UI keeps changing.

    How is this a proper product? Every time you open the desktop app the buttons may be on a completely random place

  • stymaar 31 minutes ago
    Poorly I'm afraid, given how many new bugs make their way to the claude code CLI every update.
  • nakul_ 35 minutes ago
    I wonder how they maintain the quality of tests for such a massive codebase and frequent commits.
    • owebmaster 20 minutes ago
      That's the trick: they don't
  • crooked-v 47 minutes ago
    Well, that explains the Github repo with 5000 issues, maybe about a third of which are random regressions of previous behavior.
    • AlexErrant 38 minutes ago
      I just learned that manually invoked skills MUST be the _first_ thing in the prompt, e.g. you can't have `disable-model-invocation: true` and say "Hi, /grill-me on X".

      Worse, everything after the /grill-me is injected a second time into the prompt as a <command-args> so your prompt is literally added to the context TWICE. (first time in the original user prompt.)

      I swear Anthropic is intentionally bloating your context so you burn tokens on useless bullshit like this.

      • svachalek 7 minutes ago
        Oh /loop was the crowning achievement. Basically guarantees you'll run a prompt at max context without caching over and over.
    • layman51 43 minutes ago
      I was running into something similar where I had it working on a single Python file. Maybe part of the issue is that I had memory turned off, and the conversation might have spilled into two conversations. I wasn't using version control either, but since it was a single file with about 1000 lines of code, it didn't seem too hard to eventually get all of my features back.
    • devin 37 minutes ago
      I snorted laughing at this. "We are experiencing tremendous growth" and it's just a codebase with 1,000 agents endlessly adding markdown documentation for every 1 line change.
  • typesanitizer 33 minutes ago
    FWIW, Pangram identifies several sections as 100% AI-written.
  • jstummbillig 45 minutes ago
    That's a shockingly low number.
    • t-writescode 45 minutes ago
      1000/day in what sounds like a single repo is a low number?
      • jstummbillig 42 minutes ago
        I am not sure what it is you are saying. What I am saying: I would have supposed that Claude writes 99.x% of Claude's Code code, and that ~no code at Anthropic is written by humans anymore.
        • sandeepkd 39 minutes ago
          I agree finding out who is writing that 10% of the code in the AI company is important. Maybe time to identity them and put them on PIP since they are slowing down everyone else and giving a bad name to the AI company
      • ActionHank 36 minutes ago
        to achieve what?

        Honestly not sure that there are that many effective changes a day given how little complexity there is to their public facing product.

      • oofbey 43 minutes ago
        No. 90% sounds like a low number. That implies something else is writing 10% of the code? People? Other models? What on earth is writing that other 10%?
  • JackSlateur 37 minutes ago
    90% ?

    A random twitter said that, 6 month ago, it was 100% !

    DECLINE ! SELL THE STOCK OPTIONS ! (wait, there are none, confused!)

  • ChrisArchitect 40 minutes ago
    Title is: How the Claude Code team does code review
  • mixtureoftakes 43 minutes ago
    30 thousand changes merged per day? no. like just no. what are we doing? I'm trying to understand
    • devin 33 minutes ago
      There was a post some months back called "Lines of Code Got a Better Publicist" or something along those lines. This is just more of that. I am not impressed by 30 thousand "changes" per day in the slightest without significant added context. When I logged in and prompted Claude today, do I feel like I got +600,000 change value from when I logged in a month ago?
    • JackSlateur 35 minutes ago
      I, too, can write and merge 30000 changes per day. Even 300000 if I've up to.

      Of course, just like "line of code" is a worthless metric, "change merge per day" is;

        for i in {1..10000000}
        do
          echo "I am working !" >> README.md
          git add README.md
          git commit -s -m "feat: working with AI"
        done
      
      (automerged PR, JOB IS DONE)
    • aacid 40 minutes ago
      The premise is clear, is one agent can do what developer can, but quicker, why not speed up the whole workflow to match it?
      • ActionHank 34 minutes ago
        Have you used Claude Code?

        Have you seen the benefit of the churn of 1000 PRs a day?

        • leoqa 30 minutes ago
          It’s only about 10 per engineer. I’m not at Anthropic and before 2026 I was regularly hitting 1400 commits / year on my GitHub. If agents made me 2x faster (they have, review is still slow; I currently have 40 PRs open) that’d be the same rate.
      • _verandaguy 36 minutes ago
        Right, but why do things this fast to begin with, especially for a product that's already publicly available?

        I don't want to use a product that shifts under me as I use it several times a day. I want a product that actually moves slowly and works very reliably.

        As an end user: why would I care about how many hundreds of releases a month are being pushed if maybe 1% of them have features I care about?

        Speed is not the product.

      • Andrex 34 minutes ago
        Humans don't operate at AI speeds. We're making the car go from 0 to 5000 mph in 1 second and the drivers are turning to goo in the seat.
      • sp4cec0wb0y 37 minutes ago
        More code output isn't a metric of success per se. Goodhart's law.
  • luisgvv 30 minutes ago
    And yet they can't fix the janky bugs when you scroll or show/hide chain of though, commands executed, configuring plug-ins from the options menu etc.