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.Examples
- Generate daily standup notes
- Monitor open PRs waiting for review
- Track feature progress
- See more popular use cases below
Best Practices
Test Before
To confirm your Macro prompt delivers the expected results, you can ask your question to Macroscope in Slack, or test your Macro with the “Run Now” button.
When Posting to Private Channels
To subscribe a private Slack channel to a Macro, make sure @Macroscope is added to that channel.
Popular Use Cases
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.”
Weekly Product Updates (per Area)
(Create one of these for each Area in Macroscope & publish to the appropriate Slack channel)“Summarize everything shipped in the past 7 days in the [insert area name] area. Use 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
“Generate customer-facing release notes for the past 7 days. Focus only on changes merged with the main branch that are live for customers. Focus only on changes that directly impact our customers, like new features, user-visible changes, performance improvements. Exclude internal refactoring, tests, infrastructure work. Avoid internal jargon—focus on what customers notice and would appreciate updates on.Format:
- Start with the date (Month Day, Year).
- Highlight the 4–8 most impactful changes.
- Use concise bullet points.
- Each change should include:
- A short, descriptive title (e.g., “Wiki Sidebar Improvements”, “Mobile Sidebar Fixes”).
- A 1–2 sentence description in plain, customer-friendly language, explaining what changed and why it positively impacts customers. If relevant, include an example for how customers can experience it.”
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 related to (insert feature here) 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.”
Daily IC Work Log
“Generate a summary of what everybody worked on over the last day with the following information:
- Author
- A brief description of the work committed using a flesch-kincaid reading level of 10.
- A brief description as to why the commit was made. this can be inferred if it isn’t obvious. explicitly state if you are making assumptions.
- Reference any related linear tickets only if applicable. if none are applicable, don’t mention anything (e.g. don’t say “linear tickets: none reference”).
- Express as a coherent narrative but keep brief (less than a few sentences per person)