Today, however, this is not yet implemented as an official behavior. If you want to maximize the effect of this content with Rovo now, the alternatives are: Reference the CLAUDE.md content directly in the review prompt Ex.: when asking Rovo for help in a PR, copy/paste relevant snippets from CLAUDE.md into the conversation itself (“Also consider these guidelines: …”). This ensures the model has this context in the specific thread, even if it is not read automatically from the repo. Transform the CLAUDE.md content into engineering documentation Place these same guidelines on a Confluence page and/or in a more explicit guidelines file (ex.: CONTRIBUTING.md, CODE_STYLE.md), which tends to be better recognized by tools (and also guides humans). Create PR templates that remind the reviewer (human or AI) of the rules In the PR template, add an “Important rules for this repo” section with a summary of CLAUDE.md. This way, even if Rovo does not read CLAUDE.md directly, many of the rules will be present in the PR text, which it does read.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.