docs: add t102 features to README #345
Conversation
…, model routing Update README to document the three new features from t102: - Semantic search with --semantic flag and embeddings helper - Pattern tracking with SUCCESS/FAILURE types and /patterns command - Cost-aware model routing with /route command and 5-tier guidance Also adds new slash commands to the command table.
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ 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 |
Summary of ChangesHello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on updating the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Thu Feb 5 20:35:48 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request does a great job of updating the README to include the new features for semantic memory search, pattern tracking, and model routing. The new documentation is clear, well-structured, and integrates nicely with the existing content. I've added a few minor suggestions to improve consistency in the CLI command examples.
|
|
||
| ```bash | ||
| # Enable semantic similarity search (~90MB model download) | ||
| memory-embeddings-helper.sh setup |
There was a problem hiding this comment.
For consistency with other CLI examples in this document (e.g., lines 1774-1783), it's better to use the full path for helper scripts. This ensures the commands are unambiguous and work regardless of the user's PATH configuration.
| memory-embeddings-helper.sh setup | |
| ~/.aidevops/agents/scripts/memory-embeddings-helper.sh setup |
| memory-embeddings-helper.sh setup | ||
|
|
||
| # Search by meaning, not just keywords | ||
| memory-helper.sh recall "how to optimize queries" --semantic |
There was a problem hiding this comment.
For consistency with other CLI examples in this document (e.g., lines 1774-1783), it's better to use the full path for helper scripts. This ensures the commands are unambiguous and work regardless of the user's PATH configuration.
| memory-helper.sh recall "how to optimize queries" --semantic | |
| ~/.aidevops/agents/scripts/memory-helper.sh recall "how to optimize queries" --semantic |
| pattern-tracker-helper.sh record --outcome success --task-type bugfix \ | ||
| --model sonnet --description "Structured debugging found root cause" |
There was a problem hiding this comment.
For consistency with other CLI examples in this document (e.g., lines 1774-1783), it's better to use the full path for helper scripts. This ensures the commands are unambiguous and work regardless of the user's PATH configuration.
| pattern-tracker-helper.sh record --outcome success --task-type bugfix \ | |
| --model sonnet --description "Structured debugging found root cause" | |
| ~/.aidevops/agents/scripts/pattern-tracker-helper.sh record --outcome success --task-type bugfix \ | |
| --model sonnet --description "Structured debugging found root cause" |
| --model sonnet --description "Structured debugging found root cause" | ||
|
|
||
| # Get suggestions for a new task | ||
| pattern-tracker-helper.sh suggest "refactor the auth middleware" |
There was a problem hiding this comment.
For consistency with other CLI examples in this document (e.g., lines 1774-1783), it's better to use the full path for helper scripts. This ensures the commands are unambiguous and work regardless of the user's PATH configuration.
| pattern-tracker-helper.sh suggest "refactor the auth middleware" | |
| ~/.aidevops/agents/scripts/pattern-tracker-helper.sh suggest "refactor the auth middleware" |
1 participant
Summary
/patternsand/routeto slash command tableSUCCESS_PATTERNandFAILURE_PATTERNto memory types tablemodel-routing.mdinstead ofgenerate-opencode-agents.shpattern-tracker-helper.shin self-improving agents sectionFollow-up to PR #341 (t102) which added the features but only updated counts, not descriptions.