Overview
A coding example begins with an implementer building a rate limiter.
The implementation is passed to a reviewer with no knowledge of the path used to create it. The reviewer examines the code as if it were an unfamiliar snippet found elsewhere.
It checks for:
- Incorrect behavior.
- Missing edge cases.
- Unnecessary complexity.
- Security weaknesses.
- Opportunities to simplify the design.
If the reviewer finds issues, it returns a structured issue list. A resolver then receives the code and the findings, corrects the problems, and runs tests.
The improvement does not come from giving the original agent more tokens. It comes from changing the perspective and the context.