​
How Macros Work

With Macros, you can automate recurring custom workflows—like standups, release notes, or weekly digests—by saving a prompt that runs on a schedule you set (daily or weekly). The results are then automatically broadcast into a Slack channel you specify.
FAQ: Who can create Macros?→ Any user who has access to the Macroscope web app can create Macros. They don’t need to be an Admin.

​
Examples

Macro Example

​
Best Practices

Test Before

To confirm your Macro instructions deliver the expected results, ask your question to Macroscope in Slack first.

When Posting to Private Channels

To post into a private Slack channel, share the channel ID when configuring the Macro on the web app

Daily Stand Up Notes

“Summarize all activity from the last 24 hours, grouped by contributor. Use short 1–3 bullets per person describing what they shipped and what’s still in progress. Include preview URLs for user-facing changes so teammates can easily check work.”

Weekly Product Updates

“Summarize everything shipped in the past 7 days in plain language, highlighting user-facing changes first. Use a lightweight, bulleted format with emojis for readability. Exclude technical implementation details unless they directly impact users. The audience is the entire company, which includes non-engineers.”

Release Notes

“Collect all commits and PRs tagged to a release branch in the past two weeks. Organize them into release-note style bullets that highlight user-facing changes first, then technical improvements. Exclude trivial changes (like small refactors).”

Blockers

“Analyze commits from the past 24 hours to identify tasks or contributors blocked by unresolved dependencies, missing code reviews, or outstanding PRs. List who is blocked, what they’re waiting on, and the specific issue. Keep it concise and only include cases where you are highly confident the work is actually blocked.”

Compliance Checks

“Generate a weekly summary of commits related to authentication, permissions, or data privacy.”

Track Feature Progress

“Summarize all commits tagged to the frontend-redesign area from the past 7 days. Group the commits by sub-feature (e.g. navigation, styling, component work). For each group, provide a short description of what’s been completed and what’s still in progress.”

Open PRs

“List all currently open PRs, grouped by repository. For each PR, include the title, contributor, creation date, and current status (e.g. awaiting review, review in progress, blocked). Highlight PRs that have been open for more than 3 days.”

Monthly Business Goals

“Summarize monthly activity and group it under relevant business goals. Current goals = Improve Reliability, Expand Mobile Coverage. For each goal, include 2–3 bullets describing the key engineering work completed, what’s in progress, and how it contributes to the objective. Avoid commit-level detail—keep the focus on alignment.”