Can I use this for specific commit ranges?

Yes, the skill is designed to use Git SHAs to define exactly which changes the reviewer agent should evaluate.

Why are phrases like 'You're absolutely right' forbidden?

To prevent 'performative agreement'—where the AI agrees for social comfort—ensuring every change is instead verified against the actual codebase reality.

Does it integrate with automated testing tools?

Yes, it is designed to call 'test-runner' agents and 'gambit:verify' to ensure all code passes automated checks before and after review.

How does this skill differ from standard Claude feedback?

It implements a specific, rigid workflow that mandates self-review checklists and verification steps, prioritizing technical correctness over performative agreement.

What happens if the reviewer agent gives incorrect feedback?

The skill includes a dedicated 'Push Back' protocol where you use technical reasoning and tests to challenge suggestions that are contextually incorrect.

Technical Code Review Workflow

Name: Technical Code Review Workflow
Author: Veraticus

byVeraticus

Collaboration Tools

Automates disciplined code review cycles in Claude Code through mandatory self-checks, agent dispatching, and rigorous feedback verification.

About

The Gambit Code Review skill provides a structured framework for requesting and receiving technical feedback within Claude Code. Unlike standard interactions, it enforces a 'technical rigor over social comfort' philosophy, requiring automated self-review checklists before a review is even requested. It facilitates the dispatch of specialized reviewer agents and mandates a verification protocol for all suggestions, ensuring that every implementation is technically sound, tested individually, and free from performative agreement.

Key Features

0 GitHub stars
Severity-based feedback classification (Critical, Important, Minor)
Structured reviewer agent dispatch using Git commit ranges
Strict verification protocols to prevent blind implementation of suggestions
Automated self-review checklists for tests, linters, and stubs
Integrated YAGNI (You Ain't Gonna Need It) and regression checks

Use Cases

Getting specialized technical perspectives on complex refactors or bugs
Ensuring feature completeness and code quality before merging to main
Standardizing a high-rigor development workflow across AI-assisted tasks

About

Key Features

0 GitHub stars
Severity-based feedback classification (Critical, Important, Minor)
Structured reviewer agent dispatch using Git commit ranges
Strict verification protocols to prevent blind implementation of suggestions
Automated self-review checklists for tests, linters, and stubs
Integrated YAGNI (You Ain't Gonna Need It) and regression checks

Use Cases

Getting specialized technical perspectives on complex refactors or bugs
Ensuring feature completeness and code quality before merging to main
Standardizing a high-rigor development workflow across AI-assisted tasks