code-review

Routing pull requests to the right technical reviewers requires inspecting the diff scope, inferring the primary language and framework from code and metadata, and dispatching to specialized review skills based on detected concerns like over-engineering or component composition.

Getting relevant code review feedback for multiple frameworks involves detecting the specific ecosystems present in your changes, such as Go or React, and automatically applying specialized guidance rather than relying on generic review rules.

Code review routing works with pasted snippets, selected files, git diffs, PRs, and branches by inspecting the review scope first to infer the primary technology and identify any specific review concerns present.

You can detect and simplify over-engineered code during a diff analysis when redundant checks or verbosity are identified as the main concern, which triggers routing to a dedicated simplification skill for cleanup.

Framework detection for reviewing branches is needed when multiple ecosystems or concerns appear in the changes, requiring automated identification of primary technologies to apply the correct specialized review guidance.