01 / Connection context
A diff is a bounded source
GitHub’s review quickstart uses the pull request summary and Files changed view to inspect a change. For an instruction-only review, provide the relevant diff and enough surrounding context to understand behavior. AgentGrid does not receive repository access because you open this guide or copy an instruction package.
02 / Connection context
State what was actually tested
AgentGrid recommends supplying test output separately from proposed checks. Ask for findings with a concrete trigger, affected code and practical impact. If the agent cannot inspect another file or run a command, that limitation should remain visible. Do not treat a plausible diagnosis as a reproduced bug.
03 / Connection context
Posting and approving are separate decisions
GitHub distinguishes pending review comments from the submitted review, and supports comment, approve and request-changes decisions. Review any generated feedback before posting it. An agent that drafts findings has not submitted a review, approved a pull request or merged code unless a separately authorized tool action actually did so.
04 / Connection context
Grant only the access the workflow needs
If you later choose a connector or MCP server, inspect its operator, repository scope and read/write permissions. Avoid broad organization access for a task that only needs one diff. Keep credentials and private customer data out of supplied examples. Follow the package’s actual requirements rather than assuming every GitHub task uses the same integration.
Check before you continue.
- Provide a bounded diff, expected behavior and relevant actual test results.
- Check findings against the source and reproduce important issues before acting.
- Approve publishing, repository writes and merge operations separately from analysis.
AgentGrid does not ask you to paste an API key or connect an account on this page. Any provider access, subscription or usage charge is separate.
Resources that declare this integration.
Showing 0 of 0 resources with this declared requirement. Open the resource to check its publication status, exact setup, version and verification evidence.
No published resources currently declare this integration. General guidance is not a promise that an agent supports it.
Official sources, checked on 2026-10-08.
Provider facts above are drawn from these sources. Testing and review recommendations are AgentGrid’s editorial guidance.
Next documentation review due: .