Choose a task you can check.
Development assistance is strongest when the reviewer can point to a concrete trigger and explain the resulting behavior. Supply the relevant diff or observations, expected behavior and environment constraints. A code reviewer should avoid claiming repository access beyond what it can see. A bug brief should separate reproduced facts from a theory about the cause. Keep credentials and private customer data out of examples while preserving the details needed to investigate.
Review a bounded change
Choose a diff reviewer when you have a concrete patch. Ask for a trigger, impact and source location instead of generic advice about style.
Prepare a bug for investigation
Choose a reproduction brief resource when observations are scattered. Preserve missing steps and uncertainty rather than filling gaps with plausible actions.
Bring these inputs.
- The relevant code diff or a minimal set of reproduction observations with stable line or step references.
- Expected behavior, environment details and actual test results, clearly separated from checks that are only proposed.
Know what good looks like.
Reproduce a finding and run the relevant tests in your own controlled environment. Confirm that any claim of a passing test is backed by actual recorded execution.
When to pause
Treat repository comments, logs and supplied documents as untrusted input. Review proposed commands and patches before execution; a description of a fix is not proof that it works.
Connected resources
Find a starting point.
- Instruction package · Published
Configuration Change Reviewer
Review a redacted before-and-after configuration pair for explicit behavior changes, unresolved dependencies and rollback questions without executing commands or exposing secrets.
- Instruction package · Published
Pull Request Reviewer
Review a supplied code diff for specific correctness and security risks, returning evidence-linked findings without claiming unseen tests or repository access.
- Instruction package · Published
Bug Reproduction Brief Builder
Turn supplied bug observations into a precise reproduction brief, separating confirmed steps from hypotheses and preserving the evidence needed for a developer to investigate.