@clipboard-health/ai-rules 1.6.7 → 1.6.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -89,7 +89,7 @@ These define our modeling rules, patterns, and safety constraints.
89
89
  - DEVIN ONLY: When running dbt commands in the data-modeling repository, always reuse the existing SNOWFLAKE_SCHEMA environment variable value that is already set. Do NOT replace it with a hardcoded value like "dbt_devin" - the SNOWFLAKE_SCHEMA is set to a unique per-session string and overwriting it will cause issues.
90
90
  - Use `dbt build` to verify your changes.
91
91
  - ALL dbt staging models must have strictly defined datatypes. Please Read the "Casting DBT Staging Model Datatype Heuristic" Knowledge we have. These datatypes need to defined in the yaml documentation too.
92
- - Use doc blocks for any YAML column descriptions that span across more than one model. Do NOT repeat descriptions for the same column - please reuse a doc-block!
92
+ - Always use doc blocks for YAML column descriptions (reference `models/docs.md`). Reuse existing doc blocks instead of duplicating descriptions for the same column across multiple models.
93
93
  - When adding new fields to tables keep the original source field name format, but remove any custom field prefix (**c). For example assignment_type**c should be renamed to assignment_type. Please do not hallucinate the column field names as this is misleading for users.
94
94
  - If a source table doesn't exist. Please tell the user to ask the data-team to ingest it via the relevant ETL tool.
95
95
  - A model must always have a primary/unique key. If there's no obvious one, please create a surrogate key using a combination of fields and by looking at the data. Use `dbt_utils.generate_surrogate_key` to do so.
@@ -110,7 +110,7 @@ These define our modeling rules, patterns, and safety constraints.
110
110
  - At least one column must be the primary key. This column should have both the `not_null` and `unique` tests.
111
111
  - Every column must include:
112
112
  - A `name`
113
- - A `description`. Use a doc-block if the column already exists in the `docs.md` file. If you see the same column being referenced more than once in the repo, create a doc-block for it.
113
+ - A `description`. Always use doc blocks for YAML column descriptions (reference `models/docs.md`). Reuse existing doc blocks instead of duplicating descriptions for the same column across multiple models. If they don't already exist, make them.
114
114
  - A `data_type`.
115
115
  - Include a newline between columns
116
116
  - Ensure proper YAML formatting and indentation.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@clipboard-health/ai-rules",
3
3
  "description": "Pre-built AI agent rules for consistent coding standards.",
4
- "version": "1.6.7",
4
+ "version": "1.6.9",
5
5
  "bugs": "https://github.com/ClipboardHealth/core-utils/issues",
6
6
  "devDependencies": {
7
7
  "@intellectronica/ruler": "0.3.21"