Add Snowflake cursor rules for data engineering, Cortex AI, and Snowpark/dbt#200
Add Snowflake cursor rules for data engineering, Cortex AI, and Snowpark/dbt#200jamescha-earley wants to merge 2 commits intoPatrickJS:mainfrom
Conversation
…wpark/dbt Add Snowflake-specific cursor rules covering: - Data Engineering: SQL best practices, data pipelines (Dynamic Tables, Streams, Tasks, Snowpipe), semi-structured data, Snowflake Postgres, cost optimization - Cortex AI: AI Functions (AI_COMPLETE, AI_CLASSIFY, AI_EXTRACT, etc.) and Cortex Search for hybrid vector+keyword search and RAG applications - Snowpark Python & dbt: server-side DataFrames, UDFs, UDTFs, stored procedures, and dbt-snowflake adapter with dynamic table materialization All rules grounded in official Snowflake documentation.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✅ Files skipped from review due to trivial changes (4)
📝 WalkthroughWalkthroughAdded three new Snowflake cursor rule sets (Cortex AI, Data Engineering, Snowpark Python & dbt): each includes a Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Around line 187-191: Reorder the new README entries so the list remains
alphabetically sorted within the category: move "Snowflake Cortex AI",
"Snowflake Data Engineering", and "Snowflake Snowpark Python & dbt" to their
correct positions among existing items so they appear in alphabetical order
relative to "GraphQL (Apollo Client)" and "TypeScript (Axios)"; update the
bullet sequence for the list containing "GraphQL (Apollo Client)" and
"TypeScript (Axios)" to place the three Snowflake entries where their titles fit
alphabetically.
In `@rules/snowflake-cortex-ai-cursorrules-prompt-file/README.md`:
- Around line 1-18: The README is missing source-author attribution required by
folder guidelines; add a short "Author" or "Source" credit and one-sentence
description of the .cursorrules purpose to this README.md (the file shown) so it
aligns with the .cursorrules folder policy. Specifically, update the top of
README.md (near the title or Usage section) to include an "Author: <name or
org>" line and a one-line summary like "This .cursorrules file defines Cortex AI
function usage and examples for Snowflake projects" so the file contains both
author credit and a brief purpose statement.
In `@rules/snowflake-data-engineering-cursorrules-prompt-file/README.md`:
- Around line 1-16: Add an "Author" or "Credits" section to this README
(Snowflake Data Engineering Cursor Rules) that attributes the original author of
the .cursorrules file and gives a one-line description of the file's purpose;
update the top/bottom of README.md to include a short credit line like "Original
author: <Name> — .cursorrules provides rules for Snowflake SQL and data pipeline
best practices" and mention the associated .cursorrules filename so anyone can
locate the ruleset.
In `@rules/snowflake-snowpark-dbt-cursorrules-prompt-file/.cursorrules`:
- Around line 14-18: The snippet hardcodes credentials in the
Session.builder.configs call (the session variable created via
Session.builder...create()), which is insecure; replace the literal
"user"/"password"/"account" values with secure retrieval (e.g., read from
environment variables or use Snowflake key-pair or OAuth credentials) and update
the configs expression to consume those secure values instead of plaintext;
ensure any example demonstrates using a secret source (env vars, vault, or
key-pair/OAuth) and removes the plaintext password from the
Session.builder.configs call.
In `@rules/snowflake-snowpark-dbt-cursorrules-prompt-file/README.md`:
- Around line 1-16: Add an "Original author" credit section to the README.md for
this .cursorrules set: include the original author's name (and optionally email
or GitHub handle), a one-line attribution sentence describing the .cursorrules
purpose, and a source or license link if available; place this new "Original
author" or "Credits" subsection near the top under the title or at the bottom
after "Rules Summary" in README.md so it's clearly associated with the
.cursorrules file.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 39acb62b-7e3e-4db0-b969-6f202800dee5
📒 Files selected for processing (7)
README.mdrules/snowflake-cortex-ai-cursorrules-prompt-file/.cursorrulesrules/snowflake-cortex-ai-cursorrules-prompt-file/README.mdrules/snowflake-data-engineering-cursorrules-prompt-file/.cursorrulesrules/snowflake-data-engineering-cursorrules-prompt-file/README.mdrules/snowflake-snowpark-dbt-cursorrules-prompt-file/.cursorrulesrules/snowflake-snowpark-dbt-cursorrules-prompt-file/README.md
- Sort README entries alphabetically within Database and API section - Add author attribution (Snowflake DevRel) to all 3 rule README files - Replace hardcoded credentials with env vars in Snowpark session example
Summary
All content is grounded in official Snowflake documentation.
Checklist
rules/{name}-cursorrules-prompt-file/directory.cursorrulesandREADME.mdREADME.mdupdated with entries in the "Database and API" sectionSummary by CodeRabbit