requesting-code-review

To enrich a pull request, you generate a reviewer-context bundle that analyzes git history and code metadata for changed files. This bundle aggregates authorship, churn, bug-fix rates, and ticket IDs to facilitate expert matching and risk-aware feedback.

Identifying relevant reviewers is done by analyzing dominant ownership and recent contribution patterns in git history. This expertise matching process ensures selected reviewers have the most contextual knowledge of the changed files.

Yes, you can highlight high-churn files and test coverage gaps during code review. The risk assessment mechanism maps file churn and metadata to focus reviewer attention exactly where potential technical debt and stability issues matter most.

Generating the reviewer context bundle does require TeaRAGs semantic search integration. It combines semantic search with git diff analysis to accurately map ownership, churn, and ticket connectivity for the changed files.

You prepare a code review request by asking your agent to generate the reviewer-context bundle for your current branch changes. This automatically aggregates the necessary git history, ownership data, and risk metrics into the pull request composition.