Fred
Feedback and Review Engine for Developers
Fred started in July 2026 as an answer to a problem we kept running into on our own repositories at Raw Power Labs. Reviews were where work piled up, and a large share of what reviewers spent their time on was mechanical: things that were obvious, repetitive, and already written down somewhere in our standards.
Fred is a review engine that reads a diff before a human does. It runs several different AI families over the same changes, because their perspectives differ enough that one will catch what another misses, and it grounds every review in the project's own architecture and code standard documentation so its findings match the conventions the team actually agreed on.
Reviews can go further than reporting. A fix loop will attempt the repair and review the result again across a limited number of rounds, and each run is settled as clean, disputed, or failed. Every review carries its duration and its cost in dollars, which was a deliberate decision: an agent that can loop by itself needs a visible price.
As a full-stack project it covers the interface and everything behind it, including the settings that make it configurable per team: which agents run, which providers back them, which repositories are watched, and the learnings that carry forward from one review to the next.
The goal was never to replace review. It was to make it faster and more effective, and to keep a codebase continuously at the standard you set rather than letting it drift between audits.
Year
2026
Category
AI
Front-end
UX/UI Design
Role
Full-stack developer
Made for
Raw Power Labs
A company building tooling for small, fine-tuned language models that run locally on any device, without hosted APIs
Tools and stack
Next.js, React, SQLite, Figma
Finding the bottleneck
The team's own repositories were used as the starting point, and review was identified as the place where work consistently accumulated.
Reviewing with several AI families
A pipeline was designed to run multiple AI families across the same changes, so that their differing perspectives could surface issues a single model would miss.
Grounding reviews in documentation
Reviews were anchored to the project's own architecture and code standard documentation, so that findings reflected the conventions a team had agreed on rather than generic advice.
Fix loops
An optional loop was added so that findings could be repaired and re-reviewed across a bounded number of rounds, with each run settled as clean, disputed, or failed.
Making cost visible
Duration and spend were tracked for every review and surfaced on the dashboard, so that the price of an automated loop was never hidden from the people running it.
Configuration per team
Settings were built for agents, providers, repositories, and learnings, so that each team could shape how Fred reviews and what it carries forward.