Fix CodeRabbit configuration schema validation

[DecisionNerd]

Summary

Fixes CodeRabbit configuration file to use only valid v2 schema properties, eliminating validation warnings.

Problem

CodeRabbit was showing validation errors:

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'python', 'ignore', 'tools', 
'file_types', 'comments', 'thresholds', 'integrations', 'notifications'

Solution

Removed all unrecognized properties and kept only valid v2 schema properties:

❌ Removed (not in v2 schema):

• python - Language-specific settings not supported
• ignore - Use path_filters instead
• tools - Tool configuration not exposed in config
• file_types - File type handling not configurable
• comments - Comment styling not configurable
• thresholds - Complexity thresholds not configurable
• integrations - Integration settings not configurable
• notifications - Notification settings not configurable

✅ Kept (valid v2 schema):

• language, early_access
• reviews with:
  • profile, auto_review, path_filters, instructions
• chat with auto_reply

Changes

• Cleaned up .coderabbit.yaml to minimal valid configuration
• Added YAML language server schema reference for editor validation
• Kept all important review instructions and path filters

Testing

• YAML validation passes with schema reference
• Configuration is now compliant with CodeRabbit v2 schema
• All custom review instructions preserved

Checklist

• Configuration validated against schema
• CHANGELOG updated
• No functionality lost (only removed unsupported options)
• Added schema reference for editor validation

Summary by CodeRabbit

• Chores
  • Simplified the review configuration to a leaner, review-focused setup while preserving core automation.
  • Expanded reviewer instructions with additional quality checks for correctness, error handling, tests, docstrings, performance, security, and compatibility.
  • Added guidance to prefer small PRs and flag temporary/bandaid fixes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The .coderabbit.yaml file was simplified: many nested configuration sections (checks, auto_approve, language/tool settings, ignore rules, integrations, notifications) were removed and replaced by a lean review-focused structure with expanded reviewer instructions.

Changes

Cohort / File(s)

Summary

Configuration Simplification .coderabbit.yaml

Removed extensive nested configuration (checks, auto_approve blocks, language-specific settings, ignore rules, tools, file type handling, comment/threshold settings, integrations, notifications). Kept core review automation fields (auto_review.enabled, drafts, base_branches, path_filters) and replaced detailed tooling config with concise review directives; expanded custom review instructions (openCypher semantics, error handling, test coverage, docstrings, performance, security, backward compatibility, TCK validation). Flags added for small PR preference and to call out bandaid fixes/workarounds.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly addresses the main change: fixing CodeRabbit configuration schema validation by removing unrecognized v2 schema properties.
Description check	✅ Passed	The description covers problem statement, solution details, changes made, and testing verification. However, it lacks the structured template format with type of change selection, related issues link, and testing checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/coderabbit-config

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.coderabbit.yaml (1)

32-44: ⚠️ Potential issue | 🔴 Critical

instructions is not a valid property under reviews in the v2 schema.

The schema defines "additionalProperties": false for the reviews object, and instructions (as a plain array of strings) is not a recognized property. This will produce the same validation warnings the PR aims to fix.

To provide review guidance, use path_instructions with a wildcard pattern instead:

🔧 Proposed fix using path_instructions

-  # Custom review instructions for GraphForge
-  instructions:
-    - Focus on correctness of openCypher semantics
-    - Check for proper error handling and type safety
-    - Verify test coverage for new features
-    - Ensure docstrings are present for public APIs
-    - Check for performance implications in query execution
-    - Validate that changes maintain TCK compliance
-    - Look for potential security issues (SQL injection patterns, etc.)
-    - Verify backward compatibility for API changes
-    - Prefer small, focused PRs (< 300 lines)
-    - Flag any bandaid fixes or workarounds
+  # Custom review instructions for GraphForge
+  path_instructions:
+    - path: "**/*"
+      instructions: |
+        - Focus on correctness of openCypher semantics
+        - Check for proper error handling and type safety
+        - Verify test coverage for new features
+        - Ensure docstrings are present for public APIs
+        - Check for performance implications in query execution
+        - Validate that changes maintain TCK compliance
+        - Look for potential security issues (SQL injection patterns, etc.)
+        - Verify backward compatibility for API changes
+        - Prefer small, focused PRs (< 300 lines)
+        - Flag any bandaid fixes or workarounds

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.coderabbit.yaml (1)

32-43: ⚠️ Potential issue | 🟠 Major

Replace unsupported reviews.instructions (Line 33) with reviews.path_instructions.

reviews disallows unknown keys, so using instructions directly will fail schema validation. The supported mechanism is path_instructions, which accepts a list of path-scoped instruction objects. Restructure your custom review guidance as shown below:

✅ Suggested schema‑compliant rewrite

-  # Custom review instructions for GraphForge
-  instructions:
-    - Focus on correctness of openCypher semantics
-    - Check for proper error handling and type safety
-    - Verify test coverage for new features
-    - Ensure docstrings are present for public APIs
-    - Check for performance implications in query execution
-    - Validate that changes maintain TCK compliance
-    - Look for potential security issues (SQL injection patterns, etc.)
-    - Verify backward compatibility for API changes
-    - Prefer small, focused PRs (< 300 lines)
-    - Flag any bandaid fixes or workarounds
+  # Custom review instructions for GraphForge
+  path_instructions:
+    - path: "**/*"
+      instructions: |
+        - Focus on correctness of openCypher semantics
+        - Check for proper error handling and type safety
+        - Verify test coverage for new features
+        - Ensure docstrings are present for public APIs
+        - Check for performance implications in query execution
+        - Validate that changes maintain TCK compliance
+        - Look for potential security issues (SQL injection patterns, etc.)
+        - Verify backward compatibility for API changes
+        - Prefer small, focused PRs (< 300 lines)
+        - Flag any bandaid fixes or workarounds