Code review rules your reviewer actually follows.
HeyDeer reviews against your whole repository from the first pull request. When your team has rules of its own, write them down once: HeyDeer reads REVIEW.md and AGENTS.md, and verifies your repository checks on every pull request they cover.
No seat fees · 2-click install · Free plan
---files: - "src/payments/**" - "!src/payments/**/*.test.ts"---# Charges are idempotent Every call to chargeCard() passes anidempotency key derived from the order,so a retried request never charges twice.
Four places to teach HeyDeer your codebase
Each one does a different job. Review instructions win over the files in your repository, and nothing can stop a matching repository check from running.
Repository checks
Requirements in
.agents/checks/*.md, each scoped to the files it covers. Every matching check gets a reviewer of its own, and its findings name the check.REVIEW.md
Review-only guidance: what to check, what to leave alone, how severe things are and what evidence a finding needs. Nested files add to the ones above them.
AGENTS.md and CLAUDE.md
Your coding conventions. HeyDeer reviews against them, and coding agents that support the open AGENTS.md format follow the same file.
Review instructions
Saved in HeyDeer for the workspace or one repository, so a pull request can’t change them. Only workspace admins can edit them.
Skills
Agent Skills in
.agents/skillsthat checks can call on. Reuse your Claude Code skills by linking.claude/skills.Connectors
Remote MCP servers for what the code can’t show: how a feature is used, what the logs say, a library’s docs. Paid plans only.
From a standard your team repeats to a check on every PR
- 1
Generate checks
HeyDeer reads your repository and past pull requests, then opens a PR that adds checks. No credits used.
- 2
Scope each check
List the files it covers under
files:, with!to exclude paths. - 3
Merge the checks
A person approves changes to checks; HeyDeer never auto-approves them.
- 4
Every PR is verified
Each pull request that touches covered files gets each matching check, up to 10 per review.
Rules that cut noise, too
Tell it what to leave alone
A narrow “leave alone” instruction stops a whole kind of comment you don’t want.
Skip generated code
Files marked
linguist-generatedand lock files are skipped. If every changed file is skipped, no credits are used.Decline once
Decline a finding with your reason and HeyDeer doesn’t post it again on that pull request.
Frequently asked questions
Do I have to write rules before HeyDeer can review?
No. HeyDeer reviews against the whole repository from the first review. Add guidance for the gaps your first reviews show.
Does my Claude Code REVIEW.md work with HeyDeer?
Yes, as it is. Important maps to Medium severity or above and Nit to Low. HeyDeer reads REVIEW.md from the pull request rather than the base branch, and doesn’t follow @includes.
What’s the difference between REVIEW.md and a repository check?
REVIEW.md is guidance: what to check, what to leave alone and how severe things are. A repository check is a requirement HeyDeer verifies in every pull request that changes the files it covers, with a reviewer of its own.
Can a pull request change the rules it’s reviewed by?
A PR can edit REVIEW.md, AGENTS.md or checks, but HeyDeer never automatically approves a PR that does: a person approves those changes. Review instructions saved in HeyDeer can’t be changed by a pull request at all.
Can HeyDeer write the checks for me?
Yes. Set up repository checks on the dashboard and HeyDeer reads the repository and its past pull requests, then opens a pull request that adds checks. It uses no credits.
Does HeyDeer read CLAUDE.md?
Yes. In a directory without AGENTS.md, HeyDeer reads CLAUDE.md instead. When both exist, it reads AGENTS.md.
More from HeyDeer
- Pull request reviewsEvery finding checked against your code before it’s posted.
- Fix with HeyDeerTurn findings into a tested fix pull request.
- AutopilotFixes findings, requests, failing checks and conflicts until the PR is ready.
- Coding agent PRsReview what Claude Code, Codex and Cursor write before it merges.
- Teams with reviewersHeyDeer checks the details so reviewers can focus on design.