Turn review findings into a tested fix.
Pick the findings you want fixed. HeyDeer writes the change, runs your tests in a sandbox and opens a pull request you review and merge. For anything else, mention @heydeer in a comment and it does the job where you asked.
No seat fees · 2-click install · Free plan
From finding to fix in one pull request
- 1
Choose the findings
Select Fix with HeyDeer in a review comment, or Fix findings on the review page. Add instructions if you want.
- 2
HeyDeer writes and tests
It follows your review instructions and
AGENTS.md, installs dependencies and runs your tests in a sandbox. - 3
A fix PR opens
It targets your PR’s branch and lists the changes, the findings it skipped and the tests it ran.
- 4
You merge, HeyDeer rechecks
A follow-up review checks the result, so nothing is marked fixed until the code shows it.
Ask @heydeer anywhere you write on GitHub
Mention @heydeer in a pull request or issue comment, an inline review comment or a new description. HeyDeer reads the conversation, works in a sandbox and answers where you asked, in the language you wrote in.
Explain code
Ask why a function exists or what a change affects, right on the line.
Make the change
“Fix the first issue and open an issue for the second.” Code changes go to a new pull request, so HeyDeer never overwrites work on a branch.
Check the docs
“Do the latest Next.js docs recommend this?” HeyDeer checks the documentation on the web before it answers.
Resolve merge conflicts
It can clone, resolve conflicts, push commits and open or update pull requests.
Start a review
@heydeer reviewwith an explanation re-reviews with your context, even if the code hasn’t changed.Tracked in one place
Every request is tracked under Tasks in HeyDeer. Mentions use credits.
Guardrails built in
Write access only
Fixes and mentions need write access, rechecked before every action. Opening a fix link doesn’t start an agent or spend credits.
Your branch rules apply
HeyDeer acts only in ways you could act yourself. Branch protection and other GitHub rules still decide what merges.
No forks touched
HeyDeer never pushes to a fork, pushes a fork’s commits or merges a fork’s pull request.
Frequently asked questions
Does Fix with HeyDeer push to my branch?
No. A fix opens a new pull request that targets your PR’s branch, so you review it before anything changes. On a pull request HeyDeer opened itself, it pushes to that branch instead.
Does it run my tests?
Yes. HeyDeer edits the code, installs dependencies and runs your tests in an isolated sandbox. The fix summary lists the tests it ran and any it couldn’t run.
Is Fix with HeyDeer on the Free plan?
Yes. Every plan includes Fix with HeyDeer, including Free. Fixes use credits; opening the fix page doesn’t.
How many findings can one fix handle?
Up to 100 findings, with one fix running on a pull request at a time. HeyDeer may skip a finding that no longer applies, and if no code change is needed, no pull request opens.
Who can ask @heydeer to change code?
Anyone with write access to the repository. HeyDeer rechecks that access before each action, acts only in ways that person could act themselves, and branch protection still applies.
Does a fix pull request make the review check pass?
Not by itself. After you merge the fix, a follow-up review checks the result and resolves the findings the code now addresses.
More from HeyDeer
- Pull request reviewsEvery finding checked against your code before it’s posted.
- AutopilotFixes findings, requests, failing checks and conflicts until the PR is ready.
- Rules and checksREVIEW.md, AGENTS.md and checks HeyDeer verifies on every PR.
- 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.