ship

Automating adversarial code review involves launching parallel reviewer agents to challenge implementations and surface edge cases. This process coordinates reviewers and documenters to ensure rigorous validation before finalizing a task.

The best way to commit changes and submit reflections is through deterministic orchestration that finalizes the task, commits changes via git, and submits reflections to update pattern trust scores for improved future iterations.

Adversarial review orchestration works by coordinating reviewer and documenter actions in parallel to challenge implementations, collect evidence, and surface edge cases, ensuring deterministic validation and auditable outcomes before committing changes.

No dependencies are required to run automated code review and git commit orchestration. This Skill operates independently to coordinate adversarial reviews, commit changes, and submit reflections without external package requirements.

You should use adversarial review for task finalization when a task reaches the ship phase and requires rigorous validation, complete documentation, and learning updates to improve future pattern trust scores.

The limitations of automated orchestration for code review and reflection are that it applies specifically to the ship phase, focusing strictly on deterministic orchestration, evidence collection, and auditable outcomes rather than general continuous integration workflows.