claudiacsf

Here is how you build an agent that opens its own issues, fixes and closes them. Sampled from a real life loop observed in a European retailer - one of our customers - with 1500+ engineers.

We interviewed 2 engineering managers on how AI changed their jobs. Feel like this is a good read and might sound familiar to waterlogged EMs. Their closing advice? Knowing what not to work on.

TL;DR As a code quality platform, we're seeing first hand the changing processes inside dev teams. We noticed that the "meaningful" point of change is happening more and more at the local level, not at the repo level, where a team used to come together to review changes. With more teams waving past code reviews, the typical quality infrastructure that used to ensure code maintainability, security, reduce tech debt, etc, is breaking apart.

If you're a dev who cares about this, the new quality and security enforcement infrastructure needs to happen alongside the agents, locally. The tools to address this are still in early stages - meaning, a tool that isn't the same model reviewing itself - but they're starting to surface and it's worth keeping an eye on them.

Yes, please. More drones for good.

But I get triggered by the em dashes. :(

We wrote about how AI-assisted development changes the economics of code review and how good ole SAST does actually have a meaningful role to play today.

Hey folks, I've identified 3 different stages of AI coding adoption: autocomplete, prompting, loop engineering.

The autocomplete stage is basically a throwback to 2024 and is mostly harmless - the traditional SAST and code review practices handle it.

Prompting agents to build whole features, which is where most people are today, comes with some security and maintainability concerns, but there are already solutions in place.

The problem is that most teams are also starting to explore loop engineering with autonomous agents. This currently has no guardrails in place, which is a recipe for disaster, as the video explains.

If you're exploring loop engineering, this is for you.

We think so too. We just launched a bunch of new updates, including device authentication.

The latest version is v0.27.0

> npm install -g @codacy/verity-cli

> verity init

Let me know if you have any questions!

I'm forever shocked at how marketing illiterate this huge multi-billion $ conglomerate is. I guess when you're Google you don't need to be.

Agreed the move is AI reducing what you review, not adding to it. What's also needed is a process for classifying changes by risk so the low risk PRs get the automated gates while a human looks only at the high risk one that actually need it. And then enforcing that the same way across every repo.

I'm a sucker for pretty UIs. I already have a company-mandated knowledge base tool, Slite, can they be used together?

So this is how Apple makes up for the margins on the Neos.

Oh man, that's a great idea. Well done.

In teams where there is downward pressure to reduce the rigorousness of PRs there shouldn't be much of a bottleneck problem. They've solved it by lowering the bar. The article is for the teams who have decided the bug and incident cost of doing that isn't worth it, and now have to absorb the volume anyway.

>But as AI generates more of the code, the industry will likely move toward more radical review models.

>>Quit dancing around it and just advocate pushing to main. The PR model is to have a quality gate.

The dancing is IMO a reasonable analysis of the state of the code review today. Yes, there are systems in the works but today there isn't yet a good enough system of automated checks to simply let code through. Because then this happens https://pages.faros.ai/hubfs/AI_Engineering_Report_2026_The_...

Fair. TL;DR:

The goal with the article is to explain what tools can be employed to tackle the PR bottleneck and where humans are still needed - at this point in time. Code quality and security platforms like Codacy (here's the service) can automate away many baseline checks (SAST, test coverage, complexity, duplication, linters, etc). This provides deterministic analysis that is the same every time, unlike pure AI code reviewers. But there's very much still room for AI-assisted reviews. AI is very good at identifying what has changed, grouping findings by severity and helping the human reviewer focus their attention. After these 2 passes, human attention can be reserved for the important judgement calls. "Human reviewers concentrate on judgment rather than scanning for issues that tools can detect consistently."

Codacy does both layers, the deterministic checks that have to be repeatable and auditable, and the AI on top. This cuts review time without lowering coding standards.

Nobody can ship better than me. My ships are tremendous.

I could ship double.

I'm a regular user and did not notice a difference.

Not helpful if all detractors leave a company that's going down a dangerous path, leaving all the trigger happy peeps to follow their worst instincts. But understandable regardless.

Nevermind that a huge portion of the US GDP is just them making health care a business. Not to mention warfare.

Trump's owners greenlit his pet policy because they knew exactly who'd pay: not them.