Useful evidence. Visible limits
Yanib reviews changed code and supported dependency relationships in GitHub pull requests. It does not promise to understand every language, runtime behavior, or service dependency.
Scope is explicit and directional
The source repository is included. Cross-repository context uses only authorized connected targets selected for that source. Both backend-to-backend and frontend-to-backend relationships can be relevant; a verified relationship matters, not the repository’s role or organization.
| Family | Availability | What to know |
|---|---|---|
| TypeScript imports and references | Supported structural relationships | Resolved definitions, references, and package boundaries. Dynamic behavior and unsupported resolution patterns can be missed. |
| OpenAPI and Protobuf/gRPC | Supported contracts | Producer and consumer relationships require matching contract identities and indexed evidence, not simply similar names. |
| Events and queues | Configuration-dependent | Enable the family and provide broker namespaces so supported producers and consumers can be joined safely. |
| Database dependencies | Configuration-dependent | Provide database namespace, dialect, schema, and model mappings where required. This is source analysis, not inspection of production database traffic. |
| HTTP without OpenAPI | Configuration-dependent | Provide service identity and supported client mappings. Runtime-generated URLs and dynamic routing may remain unresolved. |
| Environment and configuration | Configuration-dependent | Provide namespace and secret-key identity configuration. Equal key names in unrelated environments do not establish a dependency. |
| Infrastructure and deployment | Configuration-dependent | Provide environment and service scope, plus supported Helm or Terraform mappings where needed. It is not a live deployment topology monitor. |
Configuration is not readiness
Optional families need repository consent, valid semantic configuration, an enabled service, and an index prepared for that configuration. A saved switch alone does not prove coverage. Review your repository’s advanced Setup and the result’s coverage notes.
A review is not a test run
Bounded review of changed code can identify logic risks and explain consequences. It does not execute your test suite or guarantee a proposed fix. Verify recommendations using your build, tests, and deployment knowledge.
Partial does not mean safe
Index limits, unsupported patterns, missing access, and unavailable evidence can leave gaps. No finding means no supported issue was reported in the checked scope, not that the change is defect-free.
Review providers
PR Impact Review currently supports GitHub. GitLab repository features and Google or email sign-in do not imply GitLab merge-request impact review support.