review

Review git diff changes for naming, UI accessibility, and security vulnerabilities.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RyoMa99/dotfiles --skill review-ryoma99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/RyoMa99/dotfiles/tree/main/dot_claude/skills/review
Command: npx skills add https://github.com/RyoMa99/dotfiles --skill review-ryoma99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams catch naming ambiguities, UI accessibility and layout regressions, and security vulnerabilities in code changes before they reach a PR merge, reducing review overhead and post-merge incidents.

Core Features & Use Cases

  • Target detection: identify changed files from git diff, staged changes, or untracked files and present a selectable list of review targets.
  • Naming quality assessment: evaluate identifiers using a seven-stage taxonomy and provide concrete refactoring recommendations.
  • UI checks: run accessibility, spacing, contrast, touch target, and typography validations for component files and surface actionable fixes.
  • Security static review: detect hardcoded secrets, injection patterns, XSS risks, auth/authorization gaps, and perform dependency audit prompts with prioritized severities.
  • Concise reporting: produce per-issue findings with severity, explanation, and suggested fixes, plus a compact summary for PR reviewers.

Quick Start

Run the review skill on the current branch changes to generate naming, UI, and security findings with prioritized remediation suggestions.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code diffs for naming, UI, and security vulnerabilities?

To review code diffs for naming, UI, and security vulnerabilities, run the skill on changed files detected via git diff or staged changes. It evaluates identifier naming, UI accessibility, and static security patterns to produce prioritized remediation suggestions.

How does static security pattern detection work for pre-merge checks?

Static security pattern detection for pre-merge checks scans code changes for hardcoded secrets, injection patterns, and XSS risks. It also prompts dependency audits and outputs findings with prioritized severities to reduce post-merge incidents.

What UI accessibility and design rules are checked for component files?

UI accessibility and design rules checked for component files include validations for spacing, contrast, touch targets, and typography. The review surfaces actionable fixes for accessibility and layout regressions detected in the changed files.

Can I use git diff to identify changed files for PR code review?

Yes, you can use git diff, staged changes, or untracked files to identify changed files for PR code review. The skill detects these review targets and presents a selectable list to assess naming, UI, and security.

What is the seven-stage naming evaluation taxonomy?

The seven-stage naming evaluation taxonomy is a process applied to code identifiers to assess naming quality. It evaluates changed code to find naming ambiguities and provides concrete refactoring recommendations for improved readability.