add AI settings for roo #985
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
segoon
reviewed
Aug 5, 2025
.ai_system_prompt
Outdated
| @@ -0,0 +1,422 @@ | |||
| # roo's Memory Bank for userver Framework Projects | |||
There was a problem hiding this comment.
Looks great!
- How these texts were written/generated?
- How/when should we alter these files during userver development (e.g. adding new files, components, etc.)?
- Is there any quality control of the files? How do you know that code is generated better with these wordings rather than the others?
- How much effort should one expend to change roo to e.g. copilot or cursor?
There was a problem hiding this comment.
I've update the pr. Now there are contributor configuration and minimalistic user configuration. For now I've remove extreme user configuration - I want to work on this a bit more.
What about your questions:
- all of the text was generated with Qwen-3-Coder and Claude 4 sonnet. Please, review It carefully.
- Perfect way - delegate this to AI. I mean, we can add a ci job to process new PR and respect it changes summary in ai memory files, if needed. Rules should be periodically (something about one time per major version)
- I'm afraid we now have to rely on codeowners sight and subjective efficiency evaluation. In the future it is possible to create benchmark: for example, count of solved issues by ai with some version of memory and rules. for comparison can be used other ai: firstly, codeagent solve issue from history, secondly another ai agent compare ai solution and really approved PR.
- There is no one file in the PR, strongly related to Roo. So, we can just link (ln -s) roo rules to cursorrules or other.
There was a problem hiding this comment.
4 - can you provide make command for that? or anything to simplify it
There was a problem hiding this comment.
1 - can you provide a prompt that we can re-generate it?
Tests: CI <section id="quibbler-autodescription"> </section> commit_hash:eaee212c80d5c5c6960147e6250fc4477cfde805
commit_hash:756a92ffb41fd903da77d76c4e9fcd6c1d9587eb
Tests: протестировано CI commit_hash:eca86f7ce37efc2a03cf4918dd027ee5db5e7f11
* Add generation of empty structs to `userver/scripts/proto_structs` * Add basic tests to `userver/libraries/proto-structs/tests` * Use `google.protobuf.descriptor` instead of `google.protobuf.descriptor_pb2` * Rewrite the codegen based on extensible interfaces commit_hash:5b85213c6906946368e05c51c8be6a901d64a827
commit_hash:94cf9983ba1772dc3c2b3cf06414f02d71d3b986
commit_hash:34e8f8aa62ac36bab614c68b2eb37206b04452c3
Fixes userver-framework#161 Thanks to @sorydima for providing the initial version of this PR Tests: протестировано CI Pull Request resolved: userver-framework#983 commit_hash:bf8b7f267216bbfbf79733c375acba3488166eb0
Awaiting long requests during an active transaction (e.g. PostgreSQL, YDB, Clickhouse) is a frequently occuring bug that can easily use up the DB connection pool. This PR adds the core of the functionality to check for active transactions in heavy operations. Bugs will be reported using metrics, logs and a testpoint. commit_hash:b8fbcbe3b1db3d4a89648fae828339e4657492ac
commit_hash:ae33b89a3838b1daf984e5e2d2658c17b980f01e
commit_hash:de6cce2ea49cab94c5f873eb5a55e4f7a019e513
commit_hash:e57090aa6a40a07c13c20d78144464a9021da99f
commit_hash:d2e4e5f95613538e7d13c0161210f7c913b938a2
commit_hash:7d7089ebfe5eab640c897c4484fb6fdd86d8190a
Tests: протестировано CI commit_hash:eff1d648e49060f70131f9614816264d58dca4eb
------------------------ Note: by creating a PR or an issue you automatically agree to the CLA. See [CONTRIBUTING.md](https://github.com/userver-framework/userver/blob/develop/CONTRIBUTING.md). Feel free to remove this note, the agreement holds. Tests: протестировано CI Pull Request resolved: userver-framework#909 commit_hash:026760795ba1f936d9e50dfb7754d42cba2bf38e
Added `SSL` option to `security_protocol` parameter, that enables SSL authentication mechanism in Kafka Tests: протестировано CI Pull Request resolved: userver-framework#989 commit_hash:731daa34422e9a5550aa453d0722376604baaf1f
Resolves userver-framework#982 Tests: протестировано CI Pull Request resolved: userver-framework#988 commit_hash:c93439403b1ccdbe3d5d58f79b3abe771ae2d082
commit_hash:f4e0c73f412dfb43d94c3d76c321cec39ac10687
commit_hash:3815802b3033490f42578fa59ee7bccc86d3f699
commit_hash:fe7b17378ff530348013779c0007c83a4e93e4c6
Tests: протестировано CI commit_hash:1fc2f586f30583d78fa619cc1c12e20d786acfa9
…tional packages Tests: протестировано CI Pull Request resolved: userver-framework#986 commit_hash:bbed03b3967b24ab1e46144a293ed486cc8e56f8
commit_hash:08b1575c88952d36d5265c01a7c9447b484acba7
Tests: протестировано CI commit_hash:92cb6c80700f5e453e94c89b5838308343c8171a
commit_hash:6552753ae72cb4f80c7cf3c3e74692d067df283a
commit_hash:d24def3b21b1a6c4b5f7e52652251cc38c51be28
… files commit_hash:6aec9f1be700621e43acf66b2d5a29ea582f1dd5
Tests: not affected commit_hash:6a50a959ca0993320205e9a42a6d7920b38f7db6
Tests: checked in utests commit_hash:267441f5dfb6581753b17065ec9885932cf7f85e
* Break dependency cycles automatically if there are no annotations or options * On a dependency cycle, insert `utils::Box` at each edge of the cycle * For certain very complex cycles, `proto_structs::UnbreakableDependencyCycle` may be inserted as a last resort. If you need access to such fields, use raw protobuf message classes * Make topological sort stable for build stability and nicer output * Only forward declare types when actually needed * Clean up produced whitespace, generated code is now almost perfectly formatted * Clean up exception messages commit_hash:60e4de7b4abcda4040b22a727f773ff8776aada1
Tests: unit tests commit_hash:9b34e787390123cd3c2250bf9c0a774844bdba31
…message-typed fields commit_hash:ca503c6e14f07440b46f0a18d0bfdfdd30b3ac4a
Tests: протестировано CI commit_hash:db224c131d4ead557de38a7117aecf17bd6405f8
commit_hash:a9cf97c3cc6388701196bf91e1795e61da0ccb1b
Tests: checked in utests commit_hash:3fde291c8545863396fc20ec5160ac227b27f1ce
commit_hash:0f03e0add8df2a97bfecbfa9f2aee6347f211c6d
commit_hash:e7a75610b20a1374b00fa1d74e3b860e8605392d
commit_hash:aa8f2e30ea1934c96a626771df8149fe45d1d489
commit_hash:e0483fd2758cfe995745d4ae394dee2e2cf427b9
Original errors you can see [here](https://nda.ya.ru/t/-gukpCvU7KGHSa commit_hash:673ce77f6a5774748b3a798734c4e86a39cc9e21
Tests: CI commit_hash:0065a5b88e040a6cf34ad086fda30a9cad9b4bf2
…ments: rename memory bank folder to .ai-memory-bank, remove all except file index, simplify .roorules to basic workflow and stubs, remove complex ai-development-settings configurations
`{%- macro` -> `{% macro`
`endmacro -%}` -> `endmacro %}`
These are meaningless except when defining macros in the main jinja, which we don't do.
commit_hash:41cf792f05b998a6c7e6524d2bf91de9a8c0e54c
TryLockWithTaskContext could be called from SetupWakeups() under a started __tsan_mutex_pre_lock. As a result TSan reports an attempt to lock the mutex twice (deadlock) Tests: протестировано локально и в CI commit_hash:b63b74495fc313f9e8a6d1ef8a90e03e47489495
commit_hash:baea9edcc5836ae3409a52163cf17c252fb42894
Example:
```proto
message RepeatedDependencyOnNested {
message Foo {
repeated Bar.Inner field = 1;
}
message Bar {
message Inner {}
}
}
```
Before this PR, userver proto structs plugin mistakenly thought that it is enough to forward-declare `Bar` and/or `Bar::Inner` (within `Bar`).
It is not! This is because to mention `Bar::Inner`, `Bar` must already be defined.
The solution is to treat `WEAK` dependencies (as in: `std::vector<T>` or `utils::Box<T>`) the same way as `STRONG` dependencies when they point to a nested type.
---
Also, this PR adds support for `option (userver.structs.oneof).generated_type_name`.
commit_hash:b7b390983072beca5ee87e8f20c2dd4df6b488f2
…ments: rename memory bank folder to .ai-memory-bank, remove all except file index, simplify .roorules to basic workflow and stubs, remove complex ai-development-settings configurations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add complete configuration to use Roo Code with server
Contains:
Note: by creating a PR or an issue you automatically agree to the CLA. See CONTRIBUTING.md. Feel free to remove this note, the agreement holds.