review-team

Automated GitHub PR review uses a multi-step process orchestrating a five-member expert team and a Devil's Advocate to scrutinize findings. It utilizes the GitHub API for PR metadata and integrates with Claude Code's Task and SendMessage tools for parallel review, defense, and final report synthesis.

Adversarial code review introduces a Devil's Advocate phase that actively challenges each finding from the expert team. This defense and rebuttal mechanism filters out false positives and improves the accuracy of the final synthesized PR review report.

Yes, running this multi-step code review workflow requires both the GitHub CLI (gh) and Claude Code (claude) dependencies. The skill uses these tools to fetch PR metadata, manage parallel review communication, and synthesize the final adversarially filtered report.

Configuring project-specific PR review with Jira integration requires setting up dedicated project configuration files. This setup ensures the expert team review process can successfully fetch relevant ticket context and PR metadata to accurately synthesize the final report.

The best way to ensure critical PRs receive high-quality review is assembling a specialist expert team followed by an adversarial challenge phase. This approach guarantees a confident, adversarially filtered report by combining parallel review with a defense and rebuttal mechanism.

Automated PR review workflows require project-specific configuration to accurately integrate Jira for ticket context and properly route expert team communication. Without this setup, the multi-step orchestration cannot fetch the necessary PR metadata or synthesize a reliable final report.