dependency-review

Assess dependency PR risk by fetching PR metadata, changed files, and status checks to classify the update and guide verification for a clear merge recommendation. Provide a PR number or URL to start.

Review changeset impact by classifying the dependency update lane, such as tooling or runtime, to target verification steps and propose concrete next steps for safe merging.

Yes, evaluate failing status checks by fetching PR metadata and changed files to validate checks and propose concrete next steps for safe merging.

Classify a dependency update lane by identifying PR metadata and changed files to categorize the update as tooling or runtime, guiding targeted verification steps and merge readiness.

Dependency review works with a PR number, URL, or the current branch context, fetching metadata and status checks to classify the update and generate a clear recommendation.

Avoid automated dependency PR review when you need to assess complex runtime changes beyond metadata and status checks, as it targets tooling or runtime lane classification rather than deep behavioral testing.