review

Review code for SRP violations, complexity, performance, and readability issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thisguymartin/ai-native-dev --skill review-thisguymartin
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/thisguymartin/ai-native-dev/tree/main/.gemini/skills/review
Command: npx skills add https://github.com/thisguymartin/ai-native-dev --skill review-thisguymartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and accelerates code reviews by applying senior-architect criteria to surface Single Responsibility Principle violations, cyclomatic complexity issues, performance anti-patterns, and readability regressions so reviewers and engineers can prioritize high-impact fixes quickly.

Core Features & Use Cases

  • Clarification Protocol: Always asks scope, focus, depth, and contextual tradeoffs before beginning a review to ensure relevant and actionable feedback.
  • Review Standards: Enforces SRP, nesting and complexity limits, algorithmic and I/O performance checks, memory and redundancy detection, and naming/readability guidance.
  • Workflow & Outputs: Follows a clarify → read → analyze → report flow and returns either inline critiques with line numbers or detailed Markdown reports saved to .reviews for large audits.
  • Use Cases: Pull request reviews, architecture/feature design audits, performance optimizations, and onboarding reviews to raise code quality consistently.

Quick Start

Please review src/ and tests/ for SRP violations, excessive nesting, performance issues, and readability problems and return an inline critique with line numbers.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a code review for SRP violations and cyclomatic complexity?ā–¼

A code review for SRP violations and cyclomatic complexity applies senior-architect criteria to surface single-responsibility breaches and excessive nesting, generating structured feedback with precise line references for quick prioritization.

What is the best way to find N-plus-one and other performance anti-patterns in a pull request?ā–¼

Finding N-plus-one and performance anti-patterns in a pull request involves algorithmic and I/O checks, memory redundancy detection, and enforcing complexity limits to produce actionable inline critiques with line numbers.

How do I automate architecture audits across multi-language repositories?ā–¼

Automating architecture audits across multi-language repositories requires a clarify-read-analyze-report workflow that outputs detailed Markdown reports saved to a .reviews directory for large-scale feature design evaluations.

Can I use this code review process for CI-integrated workflows?ā–¼

Yes, this code review process suits CI-integrated workflows by applying standard review rules for readability and performance anti-patterns, returning formatted inline comments or saved markdown files directly from pipeline inspections.

Does the code review process work without providing contextual tradeoffs?ā–¼

No, the code review process mandates a clarification protocol before beginning, requiring you to define scope, focus, depth, and contextual tradeoffs to ensure the resulting readability and performance feedback is relevant and actionable.