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. As your team works with Devin throughout the week, [knowledge suggestions](/product-guides/knowledge) 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: ```txt Monday knowledge deduplication and cleanup theme={null} Review and maintain our knowledge base: 1. Triage pending suggestions from the past week: - If new and useful, propose a knowledge entry with a specific trigger description - If it overlaps with an existing entry, propose merging into the existing one - If outdated or too vague, propose dismissing it 2. Deduplicate and resolve conflicts in existing entries: - Find entries covering the same topic (e.g., two entries about Docker build steps) and propose consolidating into one - Identify entries giving contradictory advice (e.g., different pool sizes) and propose a resolution based on recency - Flag entries referencing old file paths, deprecated APIs, or removed packages ``` To get notified when each run completes, configure a **Slack channel** for the schedule — Devin will post a summary of proposed changes there so your team can review without opening the session. You need a [scheduled session](/product-guides/scheduled-sessions) so Devin has access to the knowledge management tools. 1. Navigate to **Schedules** in the left sidebar of [app.devin.ai](https://app.devin.ai/?utm_source=docs\&utm_medium=use-case-gallery), or use the **Schedule Devin** option in the input box context menu on the home page 2. Click **Create schedule** and set the frequency to **Weekly — every Monday at 8:00 AM** in your team's timezone, giving a full week of suggestions to process before the new week starts 3. Paste your Monday cleanup prompt 4. Optionally attach a [playbook](/product-guides/creating-playbooks) if you want to standardize how Devin formats new entries or organizes knowledge folders Devin sends email notifications when each scheduled run starts and completes. If your team uses the [Slack integration](/integrations/slack), Devin will also post the summary directly to your channel. For more on scheduling options, see the [Scheduled Sessions guide](/product-guides/scheduled-sessions). 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."* Once your weekly Monday cleanup is running smoothly, use these prompts in a one-off Devin session every month or two for deeper maintenance: ```txt Monthly knowledge staleness audit theme={null} Cross-check every knowledge entry against the current state of our connected repos. Flag entries that reference renamed files, removed packages, deprecated APIs, or outdated conventions. For each stale entry, propose an updated version based on what the codebase actually does today. ``` ```txt Reorganize knowledge into folders theme={null} Reorganize the knowledge base into folders: "Backend", "Frontend", "DevOps", "Testing", "API Design". Move existing entries into the right folders and update trigger descriptions to be more specific. ``` **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.

{title}