code-review

Automate code-review requests and verification within Gambit.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Veraticus/gambit --skill code-review-veraticus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Veraticus/gambit/tree/main/skills/code-review
Command: npx skills add https://github.com/Veraticus/gambit --skill code-review-veraticus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are essential for code quality but can be inconsistent and time-consuming. This Skill provides a structured approach to requesting and receiving reviews within Gambit, ensuring rigorous feedback and proper verification before changes are merged.

Core Features & Use Cases

  • Dispatch reviewer agent: Automatically assign a reviewer to a task or epic.
  • Self-review checklist enforcement: Ensure all checks are completed before requesting feedback.
  • Feedback verification workflow: Read, restate requirements, verify against code, and implement one item at a time.
  • Use Case: A developer completes a feature in a task; they trigger a code-review and systematically address reviewer feedback before merging.

Quick Start

Use gambit:code-review to initiate a review workflow on a completed Task.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review requests for completed development tasks?▼

Automating code review requests involves dispatching a reviewer agent to a task or epic, enforcing a self-review checklist, and tracking feedback with item-by-item implementation. This structured approach ensures rigorous feedback before merging changes.

What is a self-review checklist and how does it work in software engineering?▼

A self-review checklist in software engineering is a set of mandatory checks a developer completes before requesting feedback. It enforces code quality standards by requiring all items to be verified prior to dispatching a reviewer agent.

How do I verify code review feedback before implementing changes?▼

Verifying code review feedback requires reading the feedback, restating requirements, and verifying them against the code. You then implement changes one item at a time to ensure controlled, accurate updates before merging.

Can I use automated code review for both epic-driven development and task-level changes?▼

Yes, automated code review is applicable to both epic-driven development and task-level changes. It uses a native Task system to dispatch reviewers and track feedback, accommodating various scales of software engineering projects.

What is the best way to structure code reviews for consistent quality?▼

The best way to structure code reviews is through an automated workflow that dispatches reviewer agents, enforces self-review checklists, and verifies feedback systematically. This prevents inconsistent and time-consuming manual reviews.

When should I not use an automated code review workflow?▼

You should avoid automated code review workflows if your project lacks a native Task system for dispatching reviewer agents or if your development process does not support enforcing self-review checklists and item-by-item feedback implementation.