full-worktree-review

Name: full-worktree-review
Availability: InStock
Author: tktaf

Review full worktree changes against origin/main with git diff and rg.

Updated Aug 23, 2026

Search Tags:#git #quality assurance #code review #CI/CD #audit #branch review

Ready to run

npx skills add https://github.com/tktaf/codex --skill full-worktree-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: full-worktree-review
Source: https://github.com/tktaf/codex/tree/main/skills/full-worktree-review
Command: npx skills add https://github.com/tktaf/codex --skill full-worktree-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, automated review of all changes in a worktree against the origin/main branch, ensuring code quality, correctness, and adherence to project standards.

Core Features & Use Cases

Comprehensive Code Auditing: Validates changes against critical criteria like correctness, architecture, testing, documentation, and error handling.
Strict Verdicts: Delivers a definitive CLEAN or ISSUES verdict, backed by concrete evidence from the codebase.
Use Case: Before merging a feature branch, run this review to catch potential regressions, architectural violations, or missing tests that might otherwise be missed.

Quick Start

Perform a full worktree review against origin/main.

Frequently Asked Questions about full-worktree-review

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

FAQPage Schema

How do I perform a full worktree code review against origin/main?▼

Perform a full worktree code review against origin/main by executing a strict audit using git diff and ripgrep. This validates correctness, architecture, testing, documentation, and error handling, yielding a definitive CLEAN or ISSUES verdict with concrete evidence.

What is a strict worktree audit and what results does it produce?▼

A strict worktree audit is an automated verification of all worktree changes against origin/main. It produces a structured verdict of CLEAN or ISSUES, backed by concrete evidence from the codebase regarding correctness, architecture, and documentation.

How do I verify branch changes for regressions and missing tests before merging?▼

Verify branch changes by running a comprehensive code audit against origin/main. This validates testing, error handling, and architecture, catching potential regressions and missing tests before merging a feature branch.

Does this code review require specific dependencies or environments to function?▼

This code review requires git diff and ripgrep for scoped analysis against origin/main. It has no external dependencies listed, but requires explicit policy confirmations to execute its structured verdict output.

What is the best way to automate quality assurance checks on a feature branch?▼

Automate quality assurance by running a rigorous full-worktree review against origin/main. This delivers strict verdicts on code quality and adherence to project standards, ensuring potential architectural violations are caught before merging.

Why does a code review require explicit policy confirmations?▼

Explicit policy confirmations are required to ensure a strict, rigorous code review process. They enforce adherence to critical criteria like correctness and architecture before delivering a structured CLEAN or ISSUES verdict based on concrete evidence.