Dev10x:review

Analyze branch changes against a base branch and generate structured code review findings.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-review-dev10x-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:review
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/review
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-review-dev10x-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by automatically analyzing code changes and providing structured findings, improving code quality and reducing review time.

Core Features & Use Cases

  • Automated Code Review: Analyze code changes for quality and adherence to standards.
  • Structured Findings: Provide detailed feedback on issues with severity, file, line, and suggested fixes.
  • Modes: Supports both attended and unattended modes for flexibility.
  • Use Case: Before creating a PR, run Dev10x:review to automatically check for common issues and get a report of findings.

Quick Start

Run Dev10x:review to review your branch changes and ensure they meet quality standards.

Frequently Asked Questions about Dev10x:review

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

FAQPage Schema
How do I automate code review for git branch changes before a pull request?

To automate code review for git branch changes, you can run an automated review process that analyzes your changes against a base branch. This generates structured findings detailing issues, severity, and suggested fixes to improve code quality before integration.

What are structured findings in automated code quality assurance?

Structured findings in code quality assurance are detailed feedback reports generated by analyzing code changes. They categorize issues by severity, file, and line number, and provide suggested fixes to streamline the review process.

Can I run automated code checks in unattended modes for continuous integration?

Yes, you can run automated code checks in unattended modes for continuous integration workflows. The review process supports both attended and unattended execution to analyze branch changes and maintain codebase quality automatically.

Do I need pre-commit hooks and git repository access to analyze code changes?

Yes, you need pre-commit hooks and git repository access to analyze code changes effectively. The automated review process requires repository access to compare branch changes against a base branch and run automated checks.

What is the best way to maintain code quality in integrated development workflows?

The best way to maintain code quality in integrated development workflows is to automate the review process by analyzing branch changes against a base branch. This ensures adherence to standards through structured findings before integration.