Typing Your Requests
brewdata is designed to understand natural language. You don't need to use any special commands or syntax to communicate with it. Just type your request in plain English, as if you were talking to a human developer.
Effective Request Strategies
Clearly state what you want brewdata to do. Avoid vague or ambiguous language.
| Strategy | Implementation |
|---|---|
| Be specific | "Fix the bug in calculateTotal.sql that returns incorrect results" instead of "Fix the code" |
| Provide context | Use @ Context Mentions for file and code references |
| Break down tasks | Submit complex tasks in smaller manageable steps |
| Include examples | Provide sample code when you need specific formatting or style |
Example Requests
create a new file named `customers.sql` and add a create model for the `customers` table from the staging
find all instances of the column `id` in @/mart/customer.sql and replace them with `customer_id`
run the command `dbt debug` in the terminal
explain the macros `calculateTotal.sql` in @/macros/calculateTotal.sql
Common Pitfalls to Avoid
| DON'T | DO |
|---|---|
| Vague requests | Specify exactly what needs to be done |
| Assuming context | Explicitly reference files and functions |
| Excessive technical jargon | Use clear, straightforward language |
| Multiple unrelated tasks | Submit one focused request at a time |
| Proceeding without confirmation | Check the code to make sure it's complete |