When should I use the Code Review skill?

It is best used after completing major features, after every individual task in subagent-driven development, or as a final check before merging code to the main branch.

How does the skill identify which code to review?

The skill uses git SHAs (BASE_SHA and HEAD_SHA) to define the specific range of commits and changes that the subagent needs to analyze.

What happens if the reviewer finds issues?

Issues are categorized by severity. You are encouraged to fix Critical and Important issues immediately, while Minor issues can be noted for later technical debt management.

Can I disagree with the subagent's feedback?

Yes. If the reviewer provides an incorrect assessment, you should push back with technical reasoning, code samples, or test results to justify your implementation.

Code Review Orchestrator

Name: Code Review Orchestrator
Author: LangbaseInc

byLangbaseInc

•

Collaboration Tools

Facilitates systematic code reviews by dispatching specialized subagents to analyze changes and catch technical issues before merging.

About

This skill streamlines the peer review process within AI-driven development workflows by automating the handoff to a specialized code-reviewer subagent. It provides a structured framework for comparing git SHAs, identifying critical vulnerabilities or architectural flaws, and categorizing feedback into actionable tiers. By integrating review checkpoints after every task or before final merges, it ensures that code meets project requirements and maintains high quality, significantly reducing technical debt and preventing cascading errors in complex feature implementations.

Key Features

Iterative feedback support for technical pushbacks and refinements
Automated subagent dispatch for deep technical code analysis
Workflow integration for subagent-driven development cycles
Standardized issue categorization into Critical, Important, and Minor tiers
4 GitHub stars
Git-integrated review flow using specific commit ranges (SHAs)

Use Cases

Gaining fresh perspectives on complex bug fixes or large-scale refactors
Verifying task completion in subagent-driven development cycles
Conducting comprehensive quality checks before merging to main branches

About

Key Features

Iterative feedback support for technical pushbacks and refinements
Automated subagent dispatch for deep technical code analysis
Workflow integration for subagent-driven development cycles
Standardized issue categorization into Critical, Important, and Minor tiers
4 GitHub stars
Git-integrated review flow using specific commit ranges (SHAs)

Use Cases

Gaining fresh perspectives on complex bug fixes or large-scale refactors
Verifying task completion in subagent-driven development cycles
Conducting comprehensive quality checks before merging to main branches