This is a setup recipe, not a claim that a reviewer is enabled or proven on your repository. Confirm it with a finding that cites the current-head comment. Custom reviewers are in beta; see Devin’s setup and permissions.
Before you start
Install the App and recording step on the repository. Run Garnet before dependency installation and tests, including on dependency-update pull requests. The action records; the App posts the comment; the custom reviewer consumes it.Add the custom reviewer
- In Devin, open Settings → Review → Custom reviewers → Add reviewer. A Review manager must configure it.
- Name it Garnet Runtime Review, choose Plain text instructions, and paste the instructions below. Use Info finding urgency for the evidence receipt.
- Create and enable it. Under Rules, select the repositories that run Garnet. Ensure reviews cover new pull requests, pushes and pull requests marked ready, including dependency-update authors. A rule with Whenever Devin Review runs joins matching reviews but does not start a review by itself.
- Check the separate automatic-review rules too. Enabling ordinary Devin Review does not enable a custom reviewer with no matching rule.
AGENTS.md supplies session tools or review context. Creating this named reviewer and its rules is a separate step.
Copy these instructions
Verify consumption
After a recorded job finishes, request a fresh review of that same head. If the reviewer ran before Garnet finalized, its unavailable finding is expected; it does not retry or wait for the record. Open the resulting Garnet Runtime Review finding. It must cite the App comment URL and the current head, report the summary outcome with its capture limits, and name the comparison where one exists. For changed workload, check that the quoted execution chain and destination match the comment and are discussed against the diff. Devin’s Post findings to settings control whether informational findings are also posted to GitHub. They are not posted there by default. A passingDevin Review check alone does not prove consumption.
Access and timing limits
- A private OIDC-created profile may be unreadable through the MCP even after device authorization. Report the missing detail; use the head-bound App comment.
- An OIDC post-step profile lookup can return
401while the App has a record. A green workflow or successful registration alone does not prove that a profile was captured. - Missing, pending, stale or partial evidence stays unknown. Best-effort Nothing new recorded is limited to the recorded jobs and comparison, never approval.
garnet/evidence check. See the consumer contract for other reviewers and optional repository-owned mirrors.