THE METHOD · HOW FELUDA WORKS A CASE
From a push to a verdict, in five layers.
Feluda doesn't lint lines. It reads the whole case file: your diff, your codebase and your production evidence.
01 · OBSERVE
It starts with the evidence.
Every push triggers a review. Feluda pulls the diff, the files it touches, their callers, and production signals like logs and error spikes.
48,212REQUESTS SENT
7.4/sPEAK · CAP 10/s
0.3%5XX FROM YOUR APP
▪ 2xx/4xx▪ 5xx spike · 16:20 — safe mode auto-paused 40s
REQUEST #31,077 · sqli-03
agent0ms
edge2ms
checkout-api6ms
postgres1,004ms
POST/v1/coupons/apply
codeX' OR pg_sleep(1)--
500Internal Server Error1,012ms
errorQueryFailedError: canceling statement due to statement timeout
Timing leaked but not exploitable — validation agent marked as false positive. Stack trace exposure filed as FEL-147.
02 · INVESTIGATE
Hypotheses, then proof.
It forms theories about what could break, tests each against the code graph, and throws away what it can't prove.
03 · RESOLVE
Only the conclusion reaches you.
One comment per finding, ranked by severity, with the cause, the trace, and a fix you can commit in one click.
feluda/fix-refresh-race → mainCHECKS PASSING
export async function refresh(session) {- if (isExpired(token)) {+ return lock(session.id, async () => {+ if (!isExpired(await store.get(session.id))) return const next = await provider.refresh(token) await store.set(session.id, next)+ })
+3 −1 · authored by feluda · reviewed by you
YOUR CODE, YOUR RULES
What happens to your code.
NEXT · EPILOGUERetain the detective with Puku Team.→
YOUR NEXT CASE
Put Feluda on your next pull request.
Continue with PukuIncluded in Puku Team & Enterprise