tapps-review-pipeline

Coordinate parallel review-fix-validate workflows across changed files using Git worktrees.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/wtthornton/tapps-brain --skill tapps-review-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tapps-review-pipeline
Source: https://github.com/wtthornton/tapps-brain/tree/main/.claude/skills/tapps-review-pipeline
Command: npx skills add https://github.com/wtthornton/tapps-brain --skill tapps-review-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate a parallel review-fix-validate pipeline across multiple changed files. Spawns tapps-review-fixer agents in worktrees for parallel processing.

Core Features & Use Cases

  • Parallel orchestration of review, fix, and validate steps across multiple changed files.
  • Spawns tapps-review-fixer agents in dedicated worktrees with per-file instructions and scoring.
  • Merges worktree changes and triggers consolidated validation before finalizing.

Quick Start

Start the pipeline on your changed files by initiating a session, detecting changes, and launching parallel reviewers across worktrees.

Frequently Asked Questions about tapps-review-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate parallel code review across multiple changed files?

Automate parallel code review by orchestrating a review-fix-validate pipeline that spawns dedicated agents in Git worktrees for each changed file, enabling per-file scoring and automated fixes before merging changes.

What is a Git worktree pipeline for code review and when do I need it?

A Git worktree pipeline for code review coordinates simultaneous review, fix, and validation steps across changed files. Use it for multi-file code changes requiring deterministic per-file scoring and consolidated validation before finalizing.

How do I run automated fixes and validation on changed files in parallel?

Run automated fixes and validation by spawning tapps-review-fixer agents in dedicated Git worktrees with per-file instructions, then trigger consolidated validation to ensure all files pass before finalizing.

Can I use Git worktrees to process code changes in parallel without conflicts?

Git worktrees enable parallel processing of code changes by isolating per-file review and fix steps in separate working directories, merging worktree changes and triggering consolidated validation before finalizing.

What's the best way to orchestrate a review-fix-validate workflow for multi-file changes?

Orchestrate a review-fix-validate workflow by initiating a session, detecting changes, and launching parallel reviewers across Git worktrees to ensure all files pass automated fixes and validation before finalizing.

Does this parallel code review pipeline require any specific dependencies or components?

The parallel code review pipeline operates with no external dependencies, using deterministic steps with Git worktrees, session management, and verification tools to coordinate the review-fix-validate workflow across changed files.