AI code review on every pull request
I added a GitHub Actions workflow that has Claude review every pull request and post its findings. It informs review rather than replacing it: a person still approves and merges.
I’m Jon Zaro, lead developer on Burn by Cara Loren: the iOS and Android app, the API, payments, analytics and the release pipeline. I build with frontier AI models every day, from Claude Code in my editor to agent workflows that review pull requests and automate reporting.
Shipped at Burn
Burn by Cara Loren · iOS, Android, web
What changed at Burn
From the people I’ve worked with
“He picks up complex systems and tools incredibly quickly — and doesn’t just learn them, he masters them and starts making an impact right away. … Our team runs more efficiently and has more time to focus on revenue growth because of his contributions.”
“He consistently took projects from concept to deployment, seamlessly handling both frontend and backend tasks. His expertise in AI tooling, particularly integrating custom GPT models into apps, made a huge impact on project efficiency and functionality.”
“Jon is a strong engineer with a unique ability to think outside the box. While working with Jon, he was crucial in business automations utilizing various tools including AI. These automations led to saved time and efficiency as a company.”
Lead engineering on Burn by Cara Loren, a subscription fitness app on iOS, Android and the web. I own the architecture, the API, payments, analytics and the release pipeline.
Built and released v3.0 of the Burn iOS and Android app, including a progressive difficulty algorithm that adjusts workouts to each user’s performance.
Refactored the revenue reporting dashboard, cutting report prep from 2 hours to 20 minutes, and built Airtable and Zapier automations for operations.
Part of the team building a protocols app that gives firefighters fast access to procedures, drug dosages and pediatric emergency information.
AI is part of how I engineer, not a side experiment: in code review, in how I run long tasks, and in the tooling that keeps my work organized between sessions.
I added a GitHub Actions workflow that has Claude review every pull request and post its findings. It informs review rather than replacing it: a person still approves and merges.
Claude Code hooks and scheduled jobs brief each session with open work, write handoffs between sessions, turn meeting notes into action items, and generate a weekly digest and pre-meeting prep. Written in Python, with tests.
A lead model plans and reviews while smaller, cheaper models run searches and scoped coding tasks in isolated git worktrees. I read every diff and its test output before it lands.
Zapier and Airtable pipelines for operations and sales, an Instagram tracking tool that cut manual collection by 80%, and later moving a frozen Zapier pipeline into tested first-party webhooks.
Burn is a subscription fitness app on iOS, Android and the web. These are the problems I was trusted with there, from data repair to release safety, and what changed because of them.
A backfill left subscription data double-counting paying users. I contained it, repaired it in production, and made every repair reversible.
Signup and payment data ran through Zapier, and the queue had been frozen for two months. I moved it into the API with signed webhooks and tests.
An over-the-air update crashed the app on launch. I hotfixed it, wrote the postmortem, and built the gate and rollback tooling that stop a repeat.
The team was steering by an activation threshold and trial counts that were both overstated. I re-checked them against billing data and rebuilt the metrics.
I ran the cutover of the signup and checkout site from WordPress to Vercel, and proved purchase, app access and cancellation worked with real money.
Most expensive bugs I’ve fixed were wrong numbers, not crashes. I reconcile against a second source before I trust a metric.
Production data changes record their own undo. Releases have a rollback that takes minutes, not a rebuild.
A fix counts when the deployed revision includes it and the data shows the problem stopped, not when the PR merges.
I build with frontier models every day, and every change still ships with tests that fail without the fix.

A focused activity dashboard that pulls actionable work into one view. React, TypeScript, Vite and Tailwind.

A mock iOS loyalty app with authentication, point tracking and gift redemption. Expo and React Native.

A custom-trained GPT recovery coach with a no-code landing page and a Stripe paywall.
I’m based in Seattle, working globally, and open to full-stack and mobile roles across apps, payments and the systems behind them. Email is the fastest way to reach me.