review

Analyze branch code changes for security, architecture, and clarity issues.

23|4|Updated Sep 5, 2013

Search Tags:#git #architecture #code review #pull request #security #clarity

Ready to run

npx skills add https://github.com/drn/dots --skill review-drn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/drn/dots/tree/main/agents/skills/review
Command: npx skills add https://github.com/drn/dots --skill review-drn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of conducting thorough code reviews, ensuring code quality, security, and adherence to architectural best practices.

Core Features & Use Cases

Automated Code Analysis: Performs security, architecture, and clarity checks on code changes.
Contextual Review: Analyzes changes against the base branch (main/master) or a specified range.
Use Case: Before merging a pull request, use this Skill to get an immediate, detailed report on potential issues, saving valuable developer time and preventing bugs.

Quick Start

Run a code review for the current branch changes against the main branch.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate code review for a git pull request before merging?▼

Automated code review for a git pull request analyzes branch diffs and full file contents against the main branch, checking security, architecture, and clarity. It generates a consolidated report categorizing findings by severity into blocking, warning, and info levels with actionable feedback.

What is the best way to check code clarity and architecture in a branch diff?▼

Checking code clarity and architecture in a branch diff involves analyzing full file contents alongside changes against a specified base reference. This contextual review identifies architectural deviations and clarity issues, providing a categorized report of blocking and warning findings.

Can I review code changes against a specific commit range instead of main?▼

Yes, you can review code changes against a specified range or base branch like main or master. The review analyzes the diffs within that exact context, ensuring the security and architecture checks apply only to the relevant changes you target.

How does automated security code review categorize findings?▼

Automated security code review categorizes findings by severity into blocking, warning, and info levels. It analyzes branch changes for security vulnerabilities, architectural flaws, and clarity issues, generating a consolidated report that provides actionable feedback for each finding.

Do I need to specify a base reference for a branch code review?▼

Yes, specifying a base reference is required for a branch code review to analyze changes accurately. The review compares your current branch diffs and full file contents against this base branch, such as main or master, to identify security and architecture issues.