reviews

Inspect recent commits and diffs to evaluate code quality before integration.

5|2|Updated Nov 17, 2025

Search Tags:#git #maintainability #review #branch #quality-assurance #code-review

Ready to run

npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill reviews-outlinedriven

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviews
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/review
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill reviews-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently assess and improve code quality on the actively developed branch before merging.

Core Features & Use Cases

Identify recent changes and their impact on code quality and architecture.
Assess adherence to coding standards, tests, and project conventions.
Provide actionable, structured feedback and suggested improvements.

Quick Start

Review the active branch with a focus on recent commits and affected files.

Frequently Asked Questions about reviews

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

FAQPage Schema

How do I review recent git commits on a branch before merging?▼

To review recent git commits on a branch before merging, you need to identify recent changes and evaluate their impact on code quality, test coverage, and architecture. This involves inspecting commit history, diffs, and key source files to provide structured, actionable feedback.

What is the best way to ensure code quality on an active git branch?▼

The best way to ensure code quality on an active git branch is to assess adherence to coding standards and project conventions. By evaluating recent changes and their impact on architecture, you can deliver actionable feedback and suggested improvements before integration.

How do I check test coverage and project conventions in a branch code review?▼

Checking test coverage and project conventions in a branch code review requires inspecting commit history, diffs, key source files, and test status. This process evaluates recent changes to ensure they adhere to project conventions and maintain test coverage.

Can I get structured actionable feedback for git branch code changes?▼

Yes, you can get structured actionable feedback for git branch code changes by inspecting the active branch's recent commits and affected files. This evaluates code quality, test status, and adherence to conventions to deliver suggested improvements before integration.

Does a git branch code review evaluate adherence to project conventions?▼

Yes, a git branch code review evaluates adherence to project conventions by inspecting commit history, diffs, key source files, and test status. It identifies recent changes and assesses them against coding standards to provide structured feedback.

When do I need a code review for my active git branch?▼

You need a code review for your active git branch before merging to efficiently assess and improve code quality. It applies to git-based projects with branch workflows, focusing on identifying recent changes, test coverage, and architectural impact.