team-review

Educational code reviews on GitHub pull requests explain why code is risky and highlight what was done well, targeting business-logic bugs, boundary issues, and security concerns. This approach provides must-fix items, improvement suggestions, and a mergeability verdict to foster team learning.

Analyzing branch diffs for business logic validation and security concerns involves collecting changed files and context from a base branch comparison. The process identifies technical quality violations and exception issues, outputting structured review feedback including convention checks and a mergeability verdict.

To set up project context for a team code review, provide optional domain documents such as CLAUDE.md, business rules in .local.claude/biz-rules.md, and module documentation. The review process reads these files to adjust feedback depth and target specific team learning points.

Yes, you can use a branch name instead of a GitHub PR number to analyze changed files. The review process collects context by comparing the specified branch against a base branch, identifying technical quality violations and security concerns for team code review.

Yes, the team code review process checks project convention rules alongside exception issues. It outputs a structured review that includes must-fix items, nice-to-have improvements, convention checks, and a final mergeability verdict based on the analyzed branch diffs.