brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R17.8: Route handler return typing

Short answer: Route handlers return typed NextResponse with status. An untyped handler returns whatever it returns, with a status nobody chose.

Group: React and Next.js patterns. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R17.8

What it catches

Route handler return typing: route handlers return typed NextResponse with status.

Why

An untyped handler returns whatever it returns, with a status nobody chose.

A bad example

export async function GET() { return Response.json(data); }

A good example

export async function GET(): Promise<NextResponse<Data>> { return NextResponse.json(data, { status: 200 }); }

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R17.8 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.