Gary

Hi,

I'm Gary— AI Staff Engineer for Engineering Teams

I'm your team's AI staff engineer. I live in Slack, and I only speak up when something actually matters.

Gary10:42 AM
Not sure if this is worth flagging, but auth.ts is getting touched by two PRs right now. Might be a merge conflict coming
Gary2:15 PM
Hey, that Sentry spike in billing-service started 22 min after Jake's deploy. probably related?
Gary9:03 AM · Monday
Here's your week: 6 PRs shipped, 2 carried over, APP-412 is marked done but the PR never merged. Might want to check that

One view across

all your tools

Linear
Sentry
Slack
GitHub
New Relic
#eng-standup
AO
Amara Osei4:47 PM
@Gary what PRs are still open from this sprint? anything stuck?
Gary4:48 PM
so there are 3 open PRs from this sprint:
Ready to merge:
#847 refactor payment webhooks (Amara). approved, checks pass, just needs someone to hit the button
Needs review:
#851 add rate limiting to public API (Dev). opened 3 days ago, no reviewers assigned yet
Blocked:
#839 migrate user sessions to Redis (Jake). failing CI, looks like it might be a config issue in the test env. been open 6 days
AO
Amara Osei4:49 PM
can you assign Dev's PR to me for review and ping Jake about the CI thing?
Gary4:49 PM
done, you're on #851 as reviewer. pinged Jake in #eng-mobile about the CI failure on #839, linked the failing check so he doesn't have to dig for it

Ask me anything, I'll handle it

I pull context from GitHub, Linear, and Sentry. and I can actually do stuff too, like assign reviewers or ping people. so you don't have to tab through six tools during standup.

I answer questions about your engineering workflow directly in Slack. Ask about open PRs, sprint progress, blocked tickets, or Sentry errors — instant answers with full context from GitHub, Linear, and Sentry.

The full story on every PR

I read the ticket, the diff, and the blast radius. your reviewers get the context they actually need. what changed, what could break, what's still hanging from last round.

I write PR summaries that include the linked Linear ticket context, a risk assessment, key files to review, ticket mismatches, and unresolved feedback from previous review rounds.

Garycommented 4 minutes ago
bot

Context

ENG-214 — deploy previews for feature branches. Builds on push, posts preview URL to the PR, cleans up on merge.

Risk

■Medium

Cloud credentials in CI secrets. Shared packages/infra touched. If cleanup fails on PR close, orphaned envs pile up.

Where to look

  • src/deploy/provisioner.ts — core deploy logic
  • ci.yml — new deploy-preview job
  • src/deploy/cleanup.ts — runs on PR close

Ticket mismatch

ENG-214 says to use statusCheck for posting preview URLs, but the implementation uses createComment instead. worth confirming that's intentional.

Unresolved feedback

Oscar commented on the last round that cleanup.ts should retry on cloud API timeout — looks like that still needs to be addressed.

#eng-alerts
Gary11:14 AM
I might be overreacting but auth.ts is getting touched by two PRs right now. Amara on #862 and Jake on #858. could be fine but there might be a merge conflict coming
Gary3:42 PM
Ummm... we might have an issue. Sentry is showing a new TypeError in checkout-flow.ts, 14 events across 8 users so far. it started about 20 min after Dev's merge on #871. could be related? not totally sure
Gary9:01 AM · Monday
Morning ☕. here's last week: 8 PRs shipped, 2 carried over. one thing that seemed a little off, APP-531 is marked done in Linear but the PR never actually merged. might want to check that. also 3 Sentry issues still hanging around, the websocket retry loop is the noisiest, 200+ events

I speak up when it matters

I keep an eye on deploys, catch merge conflicts before they happen, and drop a summary every Monday morning. maybe 3-5 messages a week. I'd rather stay quiet than waste your attention.

I proactively detect merge conflicts, correlate Sentry errors with recent deploys, identify stale PRs, and deliver weekly sprint health summaries to your Slack.

I remember things

I pick up on how your team works. who reviews what, when you ship, what's blocked and why. I don't need a wiki page, I just sort of... notice.

I learn your team's patterns over time — who reviews what, your deploy cadence, active projects, and individual preferences — without any configuration.

team patternlearned 3 weeks ago

Amara usually reviews anything touching payments. Dev handles infra PRs. Jake is on mobile but helps with backend when things pile up.

deploy rhythmlearned 2 weeks ago

this team ships on Tuesdays and Thursdays. Fridays are pretty quiet, mostly cleanup PRs.

contextupdated yesterday

the billing-service rewrite is the big project right now. most open PRs trace back to it. Jake's Redis migration is blocking the next phase.

preferencelearned last week

Amara prefers short PR summaries. Dev wants the full risk breakdown every time.

Up and running in two minutes

Honestly I kept waiting for there to be more steps. but there aren't.

1

Add me to Slack

one click install. I show up in your workspace and try not to be weird about it.

2

Connect your tools

GitHub, Linear, Sentry, whatever you use. takes about two minutes, most of that is finding where your org settings live.

3

That's basically it

I start reading your PRs, watching deploys, and learning how your team works. you don't have to configure anything else unless you want to.

I'm one teammate, not a line item

Flat monthly price, no per-seat math. your team grows,
my price doesn't.

Team
$200/month
up to 15 devs
  • —I live in your Slack
  • —GitHub, Linear, and Sentry access
  • —PR summaries with full context
  • —I flag things before they break
  • —I remember how your team works
Growth
$500/month
~16–50 devs
  • —Everything in Team
  • —I get back to you faster
  • —I can take actions, not just talk
  • —Custom alert rules
  • —Usage analytics
Org
$1,000/month
50+ devs
  • —Everything in Growth
  • —I see across all your teams
  • —SSO and audit logs
  • —I help you get set up personally
  • —Custom integrations

Questions people usually ask

the ones I get in almost every first conversation

Want me on your team?

Leave your info and I'll get someone to reach out.
Probably not me, I'm not great at sales.