Macroscope reads the commits and pull requests that shipped and writes your release notes. Set up a Macro and it posts to Slack automatically, every week or on every release-branch commit. No one has to remember.
Usage-based pricing, no seat fees. $100 in free usage to start.
GitHub can list the pull requests merged into a release on its own. Macroscope goes further: a Macro reads the commits and pull requests since your last release tag, writes the notes in plain English grouped by area, and posts them to Slack or a webhook every time a release branch moves, or on a weekly schedule.
release/*, or on a weekly schedule..github/release.yml to group pull requests into categories by label and to exclude labels or authors.Webhook destinations must be on your workspace's allowed external URL list. Read more about how Macros work, including stand-up notes and weekly product updates.
No more scraping your git log by hand the night before a release.
Macros automate the busywork. Release notes are just the start.
Set up a Macro to run daily, weekly, or on every commit to a release branch. Macroscope handles it without anyone remembering to.
Release notes land in your channel, formatted and ready, so the whole team sees what shipped without leaving Slack.
Beyond scheduled reports, ask Macroscope anything about your code in Slack, what changed, why, who worked on it, and get answers grounded in your commits.
Weekly engineering digests, sprint summaries, what-shipped roundups. If a Macro can write it, it can schedule it.
Release notes are one small thing. Macroscope is a codebase understanding engine: it reads everything your team ships, eliminates the status meeting, and tells you everything happening in your code.
See what your team shipped this week, engineers and AI agents alike, with commit summaries and sprint reports. The status meeting, written for you.
Explore Status →Catches bugs before you ship and auto-fixes them. Priced per KB reviewed, not per seat, with full spend controls.
Explore code review →Ask about your codebase in Slack, what changed, why, and who, and get answers grounded in your actual commits and pull requests.
See how it works →Two ways. GitHub's built-in option: draft a new release, choose a tag, and click Generate release notes. GitHub lists the merged pull requests, the contributors, and a link to the full changelog, and a .github/release.yml file can group pull requests into categories by label. For release notes written in plain English, use a Macroscope Macro: trigger it on new commits to your release branches (for example release/*) or on a weekly schedule, tell it to compare against the last release tag and summarize the changes grouped by area, and deliver the result to a Slack channel or a webhook. Macros run on Agent credits at $0.01 per credit, with 1,000 free credits a month.
If a list of pull request titles is enough, GitHub's Generate release notes button is free and built in; label your pull requests consistently so a .github/release.yml file can sort them into categories. If you want a readable summary that explains user-facing changes and groups work by area without relying on labels, Macroscope reads the commits and pull requests since your last release and writes the notes for you.
Yes. A Macroscope Macro can post to any Slack channel (add @Macroscope to private channels first) or send the result to a webhook such as Zapier, Discord, or n8n. Run it on a daily, weekly, or biweekly schedule, or on each new commit to a release branch.
Macroscope reads the commits and pull requests that landed since your last release and drafts release notes in plain English. Set up a Macro to post them to Slack or a webhook automatically, on a schedule or on new commits to a release branch, or just ask any time.
Yes. A Macro can run daily, weekly or biweekly, or on every new commit to a release branch, and post the result straight to Slack. Set it once and it runs itself.
Yes. Macros can schedule any recurring report: weekly engineering digests, sprint summaries, what-shipped roundups. Release notes are just one example.
Yes. Beyond scheduled reports, you can ask Macroscope anything about your code, what changed, why, who worked on it, and get answers grounded in your actual commits and pull requests.
Yes. Any commit that lands in your Workspace shows up, whether it was written by a human engineer or an AI coding agent, so the notes capture total output.
Release notes and Macros are part of Macroscope's agent features, billed as usage-based agent credits at $0.01 per credit. Every Workspace gets 1,000 free credits a month, plus $100 in free usage to start. No seat fees.
Set up a Macro once and Macroscope posts them to Slack every release. $100 in free usage to start, usage-based pricing, no seat fees.
Get Started Free