atom

pull requests, where your team already is.

atom streams github into tidy slack threads, chases reviews for you, and runs your daily standup with a live board. install it in two minutes from your terminal, or point your coding agent at our docs.

read the docs
acts as you on githubone living thread per prmcp server for coding agents
# eng-reviews
live
approvedatom-core #412

add per-channel reminder timezones

@aria·3 commits·+128−42

aria requested a review from felix

felix: @atom approve

felix approved

mergedatom-web #318

dark mode parity for the dashboard

merged by @noah · 2 approvals

opendesign-tokens #207

move repo-channel map to remote config

@kira · waiting on review

the problem

code review should not be a guessing game.

pull requests get lost between tabs, emails, and github notifications nobody reads. reviews take hours because the right person never saw the request. engineers break their flow just to check whether anything needs them.

the problem is not your team. it is the gap between where code gets reviewed and where your team actually talks.

the solution

code review at the speed of conversation.

every pull request becomes one living thread in the channel that owns the repo. the main message carries the status, from open through changes requested and approved to merged, and edits itself in place as things happen. reviews, comments, pushes, and assignments land as tidy replies underneath.

and the thread is not just a feed. reply with @atom approve or @atom request changes needs tests and the review lands on github attributed to you. no tab switch, no bot in your review history.

inbox and insights

know what needs you. know how you are doing.

one inbox. reviews waiting on you, your prs ranked by what needs action, and everywhere you are mentioned.

real numbers. first review time, review load, first pass rate. live, medians not averages.

wherever you work. slack, your terminal, or your coding agent.

@atom inbox · @atom insights · @atom stats

@atom inboxslack · cli · mcp

needs your review

add retry logic to webhook processor (#412)

aria · waiting 2 days

migrate reminders scheduler (#398)

noah · waiting 4 hours

your pull requests

fix dm badge updates (#401)

changes requested

standup board polish (#405)

approved and ready to merge

mentioned or assigned

refactor token refresh (#396)

mentioned by kira · 1 hour ago

how it works

set up in two minutes. stay in sync from day one.

01

connect

one command signs you in with github, installs the github app and the slack bot, and maps your first repo to a channel.

terminal
$ npx @useatom/cli init signed in as you github and slack connected api → #eng-reviews

02

track

every pull request appears as one message that edits itself from open to merged. one glance shows what is moving and what is stuck.

status
[approved] #412 reminder timezones [merged] #318 dark mode parity [open] #207 remote config

03

act

reviews, comments, and pushes flow into the thread. reply to approve, request changes, assign, or label, and it lands on github as you.

#eng-reviews
you: @atom approve approved on github as you

features

github to slack, without the noise.

living pr threads

one thread per pull request. the main message flips through its states, from open to merged, editing itself in place with title, link, commits, and diff counts always current.

act as yourself

@atom approve, request changes, comment, assign, labels, close, reopen. every action runs on github under your name, not a bot account. plain language works too, like @atom lgtm.

your pr inbox

@atom inbox shows everything that needs you: reviews waiting on you, your own prs ranked by what needs action, and where you are mentioned. also in your terminal as atom inbox.

team insights

@atom insights answers with real numbers: median time to first review, publish to merge, review load, first pass rate. computed live from your prs, with the methodology published.

ci status in the thread

checks pass or fail right in the pr thread, with the failing job named and linked. approve when green without opening github.

stale pr nudges

when a pr stops moving, atom nudges the right reviewer at one day, again at two, and tells the channel at three. any activity resets the clock.

merge conflict alerts

know the moment a pr conflicts with its base branch, not at merge time. one alert in the thread, and it stays quiet once you fix it.

the monday digest

a week in review for your channel: what merged, how fast reviews went compared to last week, who carried the load, and what is stuck.

noise you can actually stand

one message per event, never two. status changes edit existing messages instead of reposting. dms only when something waits on you, with badges that update themselves when it no longer does.

pr reminders

a scheduled summary of open pull requests per channel, grouped by repo with authors and ages. drafts tagged, timezones respected. configure it with /atom reminders right in the channel.

standups without the standup bot

participants get a dm nudge, reply in plain words, and a live board in your channel fills in as updates land. same tool, one less subscription.

built for coding agents

a real cli and an mcp server ship in one package. your agent can install atom, map repos, and configure reminders and standups end to end. claude mcp add atom -- atom mcp and it speaks atom.

for coding agents

tell your agent to set it up.

every page on this site has a markdown twin, and llms.txt maps them all. point claude code or any coding agent at useatom.dev and it can read the docs, install the cli, connect github and slack, and map your repos while you watch.

claude code
$ claude "set up atom for my team by following https://useatom.dev/llms-install.md" # and give it the atom mcp server: $ claude mcp add atom -- atom mcp

who it is for

built for teams that live in slack and ship from github.

engineering leaders

you need visibility into review flow without micromanaging it. atom gives you a live view of what is open, what is blocked, and what has been sitting too long.

  • scheduled summaries of open prs per channel
  • standups with a live board, no extra bot
  • channel-level visibility without another dashboard

developers

you should not have to check github to know whether your pr moved. atom brings every review, comment, and approval into slack the moment it happens.

  • a dm only when something actually waits on you
  • @atom my prs shows everything on your plate
  • approve and review from the thread, as yourself

teams shipping continuously

your pipeline is fast. the human step is the bottleneck. atom compresses the gap between pr opened and pr reviewed.

  • notifications in seconds, not inbox digests
  • threads keep review context in one place
  • your coding agent can run the whole setup

faq

common questions

one bot for prs, reminders, and standups.

install it in two minutes from your terminal, or point your coding agent at our docs.

read the docs