LEM scoring pipeline, native MLX Metal bindings, Claude SDK wrapper, RAG with Qdrant/Ollama, unified AI facade, and MCP protocol server. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Commit Instructions
Context
When asked to commit changes in these repositories:
- All changes are pre-approved - Both tracked (modified) and untracked files have been reviewed and approved for commit
- Include everything - Commit ALL modified files AND all untracked files (including new directories)
- Don't skip files - Do not leave out untracked files assuming they need separate review
- Single commit preferred - Combine all changes into one cohesive commit unless explicitly told otherwise
The user has already validated these changes. Proceed with confidence.
Handling Ignored Files
If you see untracked directories that should typically be ignored (like node_modules/, vendor/, .cache/, dist/, build/):
- Fix the .gitignore - Create or update
.gitignoreto exclude these directories - Commit the .gitignore - Include this fix in your commit
- Don't ask - Just fix it and commit
Common patterns to add to .gitignore:
node_modules/
vendor/
.cache/
dist/
build/
*.log
.env
.DS_Store
Commit Message Style
- Use conventional commit format:
type(scope): description - Common types:
refactor,feat,fix,docs,chore - Keep the first line under 72 characters
- Add body for complex changes explaining the "why"
- Include
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Task
Review the uncommitted changes and create an appropriate commit. Be concise.