feat: rust extractor code

.changeset/breezy-aliens-cry.md

@@ -0,0 +1,6 @@
+---
+"code-recall": patch
+"code-recall-tui": patch
+---
+
+feat: add rust extractor code

.claude/commands/commit.md

@@ -0,0 +1,13 @@
+---
+description: Create a git commit with a conventional message
+allowed-tools: Bash(git add:*), Bash(git commit:*)
+model: haiku
+---
+
+# Commit Changes
+
+<git_diff>
+!`git diff --cached`
+</git_diff>
+
+Create a clear git commit message following Conventional Commits.

.claude/commands/create-github-issue.md

@@ -0,0 +1,90 @@
+Create a GitHub issue based on: $ARGUMENTS
+
+Follow these steps:
+
+1. **Parse the request**
+   - Analyze the provided description to determine issue type (bug, feature, enhancement, docs, etc.)
+   - Extract key information: title, description, context, reproduction steps (if bug)
+
+2. **Gather context**
+   - If the issue references specific code, search the codebase to understand the current implementation
+   - Identify relevant files, functions, or components that should be mentioned
+   - Check for related existing issues using `gh issue list --search "<keywords>"`
+
+3. **Determine issue labels**
+   - Use `gh label list` to see available labels
+   - Select appropriate labels based on issue type:
+     - `bug` - Something isn't working correctly
+     - `enhancement` - Improvement to existing functionality
+     - `feature` - New functionality request
+     - `documentation` - Documentation improvements
+     - `good first issue` - Suitable for new contributors
+     - `help wanted` - Extra attention needed
+
+4. **Create the issue with proper formatting**
+   Use `gh issue create` with a well-structured body:
+
+   For **bugs**:
+   ```
+   ## Description
+   [Clear description of the bug]
+
+   ## Steps to Reproduce
+   1. [Step 1]
+   2. [Step 2]
+   3. [Step 3]
+
+   ## Expected Behavior
+   [What should happen]
+
+   ## Actual Behavior
+   [What actually happens]
+
+   ## Environment
+   - OS: [e.g., macOS, Linux]
+   - Version: [relevant version info]
+
+   ## Additional Context
+   [Screenshots, logs, relevant code references]
+   ```
+
+   For **features/enhancements**:
+   ```
+   ## Summary
+   [Brief description of the proposed change]
+
+   ## Motivation
+   [Why is this change needed? What problem does it solve?]
+
+   ## Proposed Solution
+   [How should this be implemented?]
+
+   ## Alternatives Considered
+   [Other approaches that were considered]
+
+   ## Additional Context
+   [Any other relevant information]
+   ```
+
+5. **Create the issue**
+   ```bash
+   gh issue create \
+     --title "<descriptive title>" \
+     --body "<formatted body>" \
+     --label "<appropriate labels>"
+   ```
+
+6. **Confirm creation**
+   - Display the created issue URL
+   - Show issue number for reference
+
+**Example usage:**
+- `/create-github-issue Add dark mode support to the dashboard`
+- `/create-github-issue Bug: Events not being grouped correctly when fingerprint is null`
+- `/create-github-issue Improve error messages in the ingestion endpoint`
+
+**Notes:**
+- Keep titles concise but descriptive (under 72 characters)
+- Use imperative mood for feature titles ("Add...", "Fix...", "Update...")
+- Include code references using `file:line` format when relevant
+- Link to related issues or PRs if applicable

.claude/commands/fix-github-issue.md

@@ -0,0 +1,14 @@
+Please analyze and fix the GitHub issue: $ARGUMENTS.
+
+Follow these steps:
+
+1. Use `gh issue view` to get the issue details
+2. Understand the problem described in the issue
+3. Search the codebase for relevant files
+4. Implement the necessary changes to fix the issue
+5. Write and run tests to verify the fix
+6. Ensure code passes linting and type checking
+7. Create a descriptive commit message
+8. Push and create a PR
+
+Remember to use the GitHub CLI (`gh`) for all GitHub-related tasks.

apps/server/package.json

@@ -43,10 +43,11 @@
     "lint:fix": "biome check --write src tests"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "1.25.2",
+    "@modelcontextprotocol/sdk": "1.25.3",
     "@xenova/transformers": "2.17.2",
     "sqlite-vec": "0.1.7-alpha.2",
     "tree-sitter-javascript": "0.25.0",
+    "tree-sitter-rust": "0.24.0",
     "tree-sitter-typescript": "0.23.2",
     "web-tree-sitter": "0.26.3",
     "zod": "3.25.76"