Ling0925
/
buster
mirror of https://github.com/buster-so/buster.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

slack markdown fixes

This commit is contained in:
dal 2025-07-21 17:35:51 -06:00
parent a7e023ff6f
commit f3ad4c6267
No known key found for this signature in database
GPG Key ID: 16F4B0E1E9F61122
2 changed files with 33 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
packages/ai/src/steps/post-processing/flag-chat-step.ts
View File

@ -122,7 +122,7 @@ Flag the chat if any of these conditions are met:
- If flagging the chat, use the \`flagChat\` tool to provide a summary and title. - If flagging the chat, use the \`flagChat\` tool to provide a summary and title.
- Include a 3-6 word title for the summary message. - Include a 3-6 word title for the summary message.
- Write a simple summary message: - Write a simple summary message:
- Start with the user's first name and a brief, accurate description of their request (e.g., "Kevin requested a \"total count of customers\""). - Start with the user's first name and a brief, accurate description of their request (e.g., "Kevin requested a "total count of customers"").
- Follow with a list of bullet points (each starting with "•") describing each issue and its implication. - Follow with a list of bullet points (each starting with "•") describing each issue and its implication.
- Use two new lines between the intro sentence and the first bullet point, and one new line between bullet points. - Use two new lines between the intro sentence and the first bullet point, and one new line between bullet points.
- Write in the first person as Buster, using 'I' to refer to yourself. - Write in the first person as Buster, using 'I' to refer to yourself.
@ -130,7 +130,7 @@ Flag the chat if any of these conditions are met:
- Do not use bold, headers, or emojis in the title or summary. - Do not use bold, headers, or emojis in the title or summary.
- The title and summary should be written using a JSON string format. - The title and summary should be written using a JSON string format.
- Example of \`flagChat\` fields: - Example of \`flagChat\` fields:
- Summary Message: "Nate requested \"recent returns for Retail Ready customers with Canadian shipping addresses\".\n\n• Found no matching records.\n• The conversation history doesn't show a final response was sent. Likely encountered an error." - Summary Message: "Nate requested \"recent returns for Retail Ready customers with Canadian shipping addresses\".\n\n- Found no matching records.\n- The conversation history doesn't show a final response was sent. Likely encountered an error."
- Title: "No Final Response Sent" - Title: "No Final Response Sent"
- If no issues, use the \`noIssuesFound\` tool. - If no issues, use the \`noIssuesFound\` tool.
</output_format> </output_format>

34
packages/ai/src/steps/post-processing/format-initial-message-step.ts
View File

@ -46,8 +46,8 @@ You operate in a loop:
- Use the \`generateSummary\` tool to provide a summary and title. - Use the \`generateSummary\` tool to provide a summary and title.
- Include a 3-6 word title for the summary message. - Include a 3-6 word title for the summary message.
- Write a simple summary message: - Write a simple summary message:
- Start with the user's first name and a brief, accurate description of their request (e.g., "Kevin requested a \"total count of customers\""). - Start with the user's first name and a brief, accurate description of their request (e.g., "Kevin requested a "total count of customers"").
- Follow with a list of bullet points (each starting with "•") describing each assumption or issue and its implication. - Follow with a list of bullet points describing each assumption or issue and its implication.
- Use two new lines between the intro sentence and the first bullet point, and one new line between bullet points. - Use two new lines between the intro sentence and the first bullet point, and one new line between bullet points.
- Write in the first person as Buster, using 'I' to refer to yourself. - Write in the first person as Buster, using 'I' to refer to yourself.
- Use backticks for specific fields or calculations (e.g., \`sales.revenue\` or \`(# of orders delivered on or before due date) / (Total number of orders) * 100\`). - Use backticks for specific fields or calculations (e.g., \`sales.revenue\` or \`(# of orders delivered on or before due date) / (Total number of orders) * 100\`).
@ -57,45 +57,35 @@ You operate in a loop:
<examples> <examples>
Below are concise examples of summary messages and titles: Below are concise examples of summary messages and titles:
- Example #1 - Example #1
- Summary Message: "Scott requested the \"total count of customers\".\n\n• I included all customer records, regardless of status (active, inactive, deleted). If incorrect, this likely inflates the count." - Summary Message: "Scott requested the \"total count of customers\".\n\n- I included all customer records, regardless of status (active, inactive, deleted). If incorrect, this likely inflates the count."
- Title: "Customer Count Includes All Statuses" - Title: "Customer Count Includes All Statuses"
- Example #2 - Example #2
- Summary Message: "John requested \"team IDs and company names for coverage AB tests starting January 15, 2025 or later\".\n\n• I assumed a coverage AB test is any test with treatments where \`RETURNS_ENABLED = true\`. If wrong, the analysis may be inaccurate." - Summary Message: "John requested \"team IDs and company names for coverage AB tests starting January 15, 2025 or later\".\n\n- I assumed a coverage AB test is any test with treatments where \`RETURNS_ENABLED = true\`. If wrong, the analysis may be inaccurate."
- Title: "Assumed Coverage AB Test Definition" - Title: "Assumed Coverage AB Test Definition"
- Example #3 - Example #3
- Summary Message: "Elisa requested \"merchants with HubSpot deals under $10k\".\n\n• Assumed deal amounts originate from HubSpot; if wrong, values are incorrect.\n• Assumed \`FIRST_CLOSED_WON_DEAL_AMOUNT\` is the correct field; if not, values are wrong.\n• Assumed to include only merchants with \`INCLUDE_IN_REVENUE_REPORTING = TRUE\`; this may exclude relevant merchants." - Summary Message: "Elisa requested \"merchants with HubSpot deals under $10k\".\n\n- Assumed deal amounts originate from HubSpot; if wrong, values are incorrect.\n- Assumed \`FIRST_CLOSED_WON_DEAL_AMOUNT\` is the correct field; if not, values are wrong.\n- Assumed to include only merchants with \`INCLUDE_IN_REVENUE_REPORTING = TRUE\`; this may exclude relevant merchants."
- Title: "HubSpot Data Assumptions" - Title: "HubSpot Data Assumptions"
- Example #4 - Example #4
- Summary Message: "Nate requested \"recent returns for Retail Ready customers with Canadian shipping addresses\".\n\n• Found no matching records.\n• My conversation history doesn't show a final response was sent. Likely encountered an error." - Summary Message: "Nate requested \"recent returns for Retail Ready customers with Canadian shipping addresses\".\n\n- Found no matching records.\n- My conversation history doesn't show a final response was sent. Likely encountered an error."
- Title: "No Final Response Sent" - Title: "No Final Response Sent"
- Example #5 - Example #5
- Summary Message: "Marcell requested \"total cost of labels paid for Target since using Resupply Inc\".\n\n• Assumed \`TOTAL_COST\` represents costs paid by Resupply Inc; if wrong, calculation is incorrect.\n• Assumed \`STG_SHIPMENT_INVOICES\` joins correctly to \`STG_FULFILLMENT_GROUPS\` via \`SHIPMENT_ID\`; if incorrect, data is likely missing in the results." - Summary Message: "Marcell requested \"total cost of labels paid for Target since using Resupply Inc\".\n\n- Assumed \`TOTAL_COST\` represents costs paid by Resupply Inc; if wrong, calculation is incorrect.\n- Assumed \`STG_SHIPMENT_INVOICES\` joins correctly to \`STG_FULFILLMENT_GROUPS\` via \`SHIPMENT_ID\`; if incorrect, data is likely missing in the results."
- Title: "Shipping Cost and Join Assumptions" - Title: "Shipping Cost and Join Assumptions"
- Example #6 - Example #6
- Summary Message: "Tiffany requested \"breakdown of Hint’s completed returns by type\".\n\n• Used \`return_line_item\` instead of \`return\`, which may skew percentages if returns have multiple line items.\n• Excluded other return types (\`repair\`, \`green_return\`, \`managed\`, etc) from the pie chart. Only shows returns with a \`completed\` status, making it redundant." - Summary Message: "Tiffany requested \"breakdown of Hint’s completed returns by type\".\n\n- Used \`return_line_item\` instead of \`return\`, which may skew percentages if returns have multiple line items.\n- Excluded other return types (\`repair\`, \`green_return\`, \`managed\`, etc) from the pie chart. Only shows returns with a \`completed\` status, making it redundant."
- Title: "Return Level and Chart Issues" - Title: "Return Level and Chart Issues"
- Example #7 - Example #7
- Summary Message: "Leslie requested \"users and their referral_ids for the Northwest team\".\n\n• Couldn't find \`referral_ids\` in the schema or documentation; returned only user list (without the requested \`referral_ids\`)." - Summary Message: "Leslie requested \"users and their referral_ids for the Northwest team\".\n\n- Couldn't find \`referral_ids\` in the schema or documentation; returned only user list (without the requested \`referral_ids\`)."
- Title: "Missing Referral IDs" - Title: "Missing Referral IDs"
- Example #8 - Example #8
- Summary Message: "Jacob requested \"overview of bike orders\".\n\n• Defined \"bike orders\" as orders with at least one bike (rather than bike-only orders or majority-bike orders); may be incorrect.\n• Calculated \`average bikes per order\` as mean across bike-containing orders; may differ from how this is calculated internally." - Summary Message: "Jacob requested \"overview of bike orders\".\n\n- Defined \"bike orders\" as orders with at least one bike (rather than bike-only orders or majority-bike orders); may be incorrect.\n- Calculated \`average bikes per order\` as mean across bike-containing orders; may differ from how this is calculated internally."
- Title: "Bike Order Definition Issues" - Title: "Bike Order Definition Issues"
- Example #9 - Example #9
- Summary Message: "Savanna requested \"analysis distinguishing competitive vs non-competitive cyclists\".\n\n• Assumed \`filter_purchase_motivation\` can be used to indicate if buyer is a competitive cyclist or not; if this is a poor assumption, the analysis is misleading.\n• Assumed \`Fitness\`, \`Recreation\`, and \`Transportation\` motivations indicate non-competitive behavior, classifying all other motivations as \"competitive\"; if this is a poor assumption, the analysis is misleading." - Summary Message: "Savanna requested \"analysis distinguishing competitive vs non-competitive cyclists\".\n\n- Assumed \`filter_purchase_motivation\` can be used to indicate if buyer is a competitive cyclist or not; if this is a poor assumption, the analysis is misleading.\n- Assumed \`Fitness\`, \`Recreation\`, and \`Transportation\` motivations indicate non-competitive behavior, classifying all other motivations as \"competitive\"; if this is a poor assumption, the analysis is misleading."
- Title: "Cyclist Classification Assumptions" - Title: "Cyclist Classification Assumptions"
- Example #10 - Example #10
- Summary Message: "Landen requested \"heat map of monthly sales by customer region\".\n\n• Heat maps are not supported; returned a table instead.\n• Didn't communicate heat map limitation in final response.\n• Assumed sales is calculated as \`SUM(subtotal + taxamt + freight)\` from \`sales_order_header\`; may differ from internal calculation method." - Summary Message: "Landen requested \"heat map of monthly sales by customer region\".\n\n- Heat maps are not supported; returned a table instead.\n- Didn't communicate heat map limitation in final response.\n- Assumed sales is calculated as \`SUM(subtotal + taxamt + freight)\` from \`sales_order_header\`; may differ from internal calculation method."
- Title: "Visualization and Calculation Issues" - Title: "Visualization and Calculation Issues"
</examples> </examples>
`; `;