Parallel Code Review FAQs

Question 1

What is TDD and Beads compliance?

Accepted Answer

It checks if your code follows Test-Driven Development patterns and ensures that every change is correctly linked to an issue in the Beads tracking system with appropriate labels like tdd-red or tdd-green.

Question 2

How does the parallel subagent system work?

Accepted Answer

The skill uses the Task tool to launch five independent Sonnet agents simultaneously. Each agent is given a specific persona—such as Architect or TypeScript Expert—to analyze the code diff through that unique lens.

Question 3

Can this skill be used with GitHub Pull Requests?

Accepted Answer

Yes, it is designed to work with the GitHub CLI (gh pr diff) to pull remote changes, as well as local git diffs for pre-commit reviews.

Question 4

Does it replace standard linters?

Accepted Answer

No, it is designed to complement linters. The agents are instructed to ignore formatting and style issues that automated tools catch, focusing instead on logic, safety, and architectural debt.

Question 5

How are the findings from five different agents managed?

Accepted Answer

The skill includes a synthesis step that deduplicates overlapping issues and prioritizes them by severity, ensuring the final report is actionable and high-signal.

Parallel Code Review

Key Features

Use Cases

Parallel Code Review

Key Features

Use Cases