See it in action
Reviews that
actually help
Not a wall of generic comments. Gaston gives you a structured verdict: severity-tagged findings, concrete fixes, and a clear recommendation. Every comment earns its place.
✓Security vulnerabilities flagged with fixes
✓Performance bottlenecks with alternatives
✓Clear severity: blocker vs suggestion
✓Merge-readiness verdict on every PR
Instant reviews
Every PR reviewed in minutes. No waiting for teammates.
Higher code quality
Catches security, performance, and logic bugs humans miss.
Zero extra work
No config, no new habits. Just open a PR.
packages/db/src/pipeline-events.ts
1import { pool } from './connection';
2import type { PipelineEvent } from './types';
3
4/** Must never block the review pipeline */
5export async function insertPipelineEvent(
6 event: PipelineEvent
7) {
8 try {
9 await pool.query(
10 'INSERT INTO pipeline_events ...',
11 [event.type, event.payload]
12 );
13 } catch (err) {
14 console.error('telemetry write failed', err);
15 }
16}
17
18export async function insertPipelineEvents(
19 events: PipelineEvent[]
20) {
21 const client = await pool.connect();
22 await client.query("SET statement_timeout = '5000'");
⌄Comment on line R22
gaston-reviewbot1 hour ago···This mutates session state on a pooled connection. After
client.release(), the next borrower inherits a 5s timeout. Use SET LOCAL inside a transaction to scope it properly.☺
Resolve comment
23 for (const e of events) {
24 await client.query('INSERT INTO ...', [e]);
25 }
26 client.release();
27}
gaston-reviewbot🔄 Changes Requested
6/10
Both helpers are documented as “must never block the review flow” but they synchronously await Postgres writes. If DB is slow, the pipeline stalls despite error swallowing.
📌 2 inline comments
await pool.query()keeps the caller blocked on DB latency. This contradicts the “must never block” contract. Move insert off the critical path or use bounded timeout with drop semantics.