feat: Add sql-query-explainer kit#150
Conversation
This configuration defines the SQL Query Explainer workflow, detailing its purpose, version, author, tags, steps, and relevant links.
This document outlines the SQL Query Explainer AgentKit template, detailing its purpose, operational flow, and use cases for understanding SQL queries without execution.
This README provides an overview of the SQL Query Explainer workflow, detailing its purpose, output structure, use cases, prerequisites, and usage instructions.
This file implements a SQL Query Explainer flow that accepts a raw SQL query and returns a structured JSON explanation, including a summary, clause breakdown, performance concerns, and optimization suggestions.
Add structured explanation format for SQL query analysis.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Validation ResultsNew Contributions Detected
Check Results
Errors
🛑 Please fix the errors above before this PR can be merged. Refer to CONTRIBUTING.md and CLAUDE.md for the expected folder structure. |
|
Submitting as part of the Lamatic This kit adds a SQL Query Explainer agent — accepts any SQL query, returns a structured JSON explanation with summary, clause-by-clause breakdown, performance concerns, and optimisation suggestions. Please apply the |
PR Checklist
1. Select Contribution Type
kits/<category>/<kit-name>/)bundles/<bundle-name>/)templates/<template-name>/)2. General Requirements
kebab-caseand matches the flow IDREADME.md(purpose, setup, usage)3. File Structure (Check what applies)
config.jsonpresent with valid metadata (name, description, tags, steps, author, env keys)flows/<flow-name>/(where applicable) include:config.json(Lamatic flow export)inputs.jsonmeta.jsonREADME.md.env.examplewith placeholder values only (kits only)config.jsonnode graphs (changes via Lamatic Studio export)4. Validation
npm install && npm run devworks locally (kits: UI runs; bundles/templates: flows are valid)[kit] Add <name> for <use case>)