AI code review that follows your CLAUDE.md and AGENTS.md
Solemly treats the instruction files you already keep for coding agents as review guidelines. It finds CLAUDE.md, AGENTS.md, REVIEW.md, CONVENTIONS.md, .cursorrules, .windsurfrules, copilot-instructions.md and similar files anywhere in the repository, reads them at the pull request's own commit, and reviews each change against them.
Checked against the product on 2026-11-03.
Files Solemly reads
It looks for these files anywhere in the repository, matching names regardless of case:
| File | Typically used by |
|---|---|
CLAUDE.md | Claude Code |
AGENTS.md | Codex and other coding agents |
REVIEW.md | Review-only rules |
CONVENTIONS.md, STYLE.md, STYLEGUIDE.md | Style guides |
.cursorrules, and anything under .cursor/rules/ | Cursor |
.windsurfrules | Windsurf |
copilot-instructions.md | GitHub Copilot |
Any .md file inside a .claude/ directory | Claude Code |
Files in subdirectories apply too, so a CLAUDE.md next to a package can hold rules for that part of the codebase.
How they're used
For each review, Solemly reads these files from the pull request's own commit, so a change to your rules in the same pull request applies to its review. Short, specific rules work better than long documents.
Writing good review rules
- Be specific. Use `logger` from `lib/log`, never `print` works better than follow our logging practices.
- Say what matters. Point out the mistakes you see most often in review.
- Say what to ignore. For example, Don't comment on formatting: it's enforced by the formatter.
Put rules that are only for reviews in REVIEW.md, for example Flag any new endpoint without an authorization check. Rules your coding agents should also follow belong in CLAUDE.md or AGENTS.md.
See what it found
The Context page in Solemly lists the instruction files found in each repository and lets you read them. It shows the files on the repository's default branch, while reviews read them at the pull request's commit.
Rules versus settings
Instruction files hold guidance in prose. For settings, and for instructions that apply only to some paths, use a .solemly.yaml in the repository or Repository Settings: skip bot pull requests, leave files out, add instructions per path and set how strict reviews are.
Questions
Do I need a separate file for Solemly?
No. It reads the CLAUDE.md, AGENTS.md, Cursor rules and similar files you already keep. If you want rules that apply only to reviews, put them in a REVIEW.md.
Does it read instruction files in subdirectories?
Yes. Files anywhere in the repository apply, so a CLAUDE.md next to a package can hold rules for that part of the codebase.
What if a pull request changes the rules?
The review uses the new version. Solemly reads the files from the pull request's own commit, so a change to your rules in the same pull request applies to its review.
Where can I see which files it found?
On the Context page in Solemly, which lists the instruction files found in each repository on its default branch and lets you read them.
In the docs
Related
Try it on your next pull request
Free for 14 days with every feature, no credit card. Install it on a repository and the next pull request gets reviewed.