Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.devin.ai/llms.txt

Use this file to discover all available pages before exploring further.

Give your team a weekly wrap-up without the Friday afternoon scramble. Every Friday, Devin compiles every merged PR across your tracked repos, groups them into categories (Features, Fixes, Docs, Infra), writes a human-readable summary, and posts it to Slack — giving engineering, product, and leadership a shared view of what shipped.

Use this template

Open Weekly Changelog in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for Weekly Changelog.

​
What this automation does

The Weekly Changelog automation solves a universal pain: nobody wants to compile the weekly update manually, but everyone wants the update. Devin reads git log across your repos, filters to merged PRs, reads each PR title and description for user-facing context, and writes the summary in the format your team has standardized on.

​
How it works

Trigger: Schedule event — recurring
  • Event: schedule:recurring
    • Conditions:
      • rrule matches FREQ=WEEKLY;BYDAY=FR;BYHOUR=16;BYMINUTE=0
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Weekly Changelog. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Engineering teams that need to communicate progress to non-engineer stakeholders
  • Founders and leadership who want a zero-effort pulse on shipping velocity
  • Cross-team visibility across a large engineering organization
  • Building a historical archive of releases and changes

​
Customization ideas

  • Change the cadence to daily, biweekly, or monthly
  • Target specific Slack channels per audience (eng, leadership, product)
  • Cross-post to Notion or your internal wiki for persistence
  • Customize the format — release notes, executive summary, Twitter-ready blurbs

​
See also