Coding · Intermediate

Managing shared programming gotchas across developer tools

Look up verified gotchas before writing code and record newly discovered fixes

Use with BotBento Markdownالعربية

Opens BotBento. Paste the prompt into a bot; nothing is preconfigured.

  1. When you askReceive coding request
  2. ThenCheck knowledge base for caveats
  3. ResultDraft code and propose new tip

Before implementing code changes, the bot queries a local or shared knowledge database for known traps and version gotchas related to the task. When you encounter or correct a stale dependency, incorrect configuration, or recurring bug, the bot summarizes the lesson and submits a draft entry for approval.

Prompt to start with

BotBentoRecommended
When assigned a development task, search the knowledge database for documented caveats, outdated patterns, and repo-specific fixes before writing code. Apply any confirmed insights to your solution. If you encounter an undocumented gotcha or the developer corrects your code, draft a structured knowledge unit describing the problem and fix. Ask for explicit approval before publishing, sending, or deleting any entries in the shared database.