devlyn:team-review

A multi-perspective code review assembles specialized reviewer roles to analyze a pull request diff, covering security, code quality, testing, and performance. The process classifies changed files to assign targeted reviewers and merge cross-cutting issues for comprehensive validation.

Automating security and quality assurance checks involves orchestrating a deterministic team workflow that selects reviewer roles based on git diff discovery. It validates branch changes by executing tests and lint gating to reduce the risk of shipping bugs across multiple expert domains.

Yes, structured review workflows can assess UX/UI, accessibility, and API contract changes. The review lead dynamically assembles optional specialized reviewer roles depending on the specific change type identified in the repository diff, ensuring all product behavior domains are evaluated.

An agent team coordinates diff analysis through a phased process managed by a review lead. The lead handles team creation, task creation, and task assignment based on the changed files, followed by cross-cutting issue merging and final validation to ensure thorough coverage.

No, you do not need to provide a changeset manually to start a thorough code review. The workflow begins with git diff discovery to automatically collect and classify modified files, then selects the appropriate reviewer roles to initiate the multi-perspective analysis.