Weekly Knowledge Deduplication and Cleanup

Don’t want to set this up manually? Paste a link to this page into a Devin session and ask it to set everything up for you.

Write your Monday cleanup prompt

As your team works with Devin throughout the week, knowledge suggestions accumulate from every session — patterns Devin learned, commands that worked, conventions it discovered. By Friday, you might have a dozen new suggestions waiting alongside existing entries that reference renamed files or deprecated APIs. A recurring Monday morning Devin session can process all of this before your team starts the week.Your prompt should cover two jobs: triaging the past week’s suggestions, and deduplicating existing entries. Here’s a prompt that handles both:To get notified when each run completes, add a Post to Slack notification to the automation — Devin will post a summary of proposed changes there so your team can review without opening the session.

Create the Monday 8 AM automation

Run the cleanup as an automation with a Schedule trigger so a Devin session with access to the knowledge management tools starts every week.

Navigate to Automations in the left sidebar of app.devin.ai and click Create automation
In the trigger dropdown, expand Schedule and choose Every week — every Monday at 8:00 AM in your team’s timezone, giving a full week of suggestions to process before the new week starts
Paste your Monday cleanup prompt
Optionally @-mention a playbook in the prompt if you want to standardize how Devin formats new entries or organizes knowledge folders

Under Notifications, add an Email notification to get an email when each run completes. If your team uses the Slack integration, add Post to Slack so Devin posts the summary directly to your channel. For more on scheduling options, see Schedule triggers.

Review and approve the first Monday run

After the first Monday run completes, open the session to review what Devin proposes. Devin does not automatically apply knowledge changes — it proposes creates, merges, and deletions, and you manually approve or reject each one. A typical summary looks like this:

Knowledge Deduplication & Cleanup — Monday, Feb 10

Proposed new entries (3):
  - "Run prisma migrate deploy before integration tests" — from session #4821
  - "Redis cache TTL for user profiles is 5 minutes" — from session #4835
  - "Use vitest, not jest, for frontend unit tests" — from session #4802

Proposed merges (2):
  - Consolidate "Docker build steps" + "Container build process" → single entry
  - Merge two overlapping entries about API error handling conventions

Proposed removal (1):
  - "Bundle with webpack" — project migrated to Vite in December

Proposed dismissals (4 suggestions):
  - Already covered by existing knowledge

Conflict resolution (1):
  - Two entries disagreed on connection pool size (5 vs 10)
  - Recommends pool_size=10 based on the more recent performance tuning session

Review each proposal and approve or reject it from the session. Use the first few runs to calibrate — if Devin is too aggressive about proposing removals, add a note to your prompt: “When in doubt, keep the entry and flag it for review rather than proposing removal.”

Go deeper with monthly audits

Once your weekly Monday cleanup is running smoothly, use these prompts in a one-off Devin session every month or two for deeper maintenance:Tip: The weekly Monday schedule handles ongoing deduplication and suggestion triage. These deeper audits — coverage gap analysis and folder reorganization — are one-time tasks best run manually every month or two.