review-code

Review Git diffs for i18n, permissions, Firestore indexes, and security issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/maxton76/stall-bokning --skill review-code-maxton76
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/maxton76/stall-bokning/tree/main/.claude/skills/review-code
Command: npx skills add https://github.com/maxton76/stall-bokning --skill review-code-maxton76

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates in-depth code reviews, catching project-specific architectural concerns, potential bugs, security vulnerabilities, and adherence to best practices that standard linters might miss.

Core Features & Use Cases

  • Multi-faceted Analysis: Checks for i18n gaps, permission issues, Firestore index needs, API alignment, breaking changes, quality standards, logic errors, and security flaws.
  • Context-Aware: Understands the EquiDuty monorepo structure and project-specific patterns.
  • Use Case: Before merging a new feature, run this Skill to ensure all API endpoints are properly secured, all user-facing strings are localized, and no critical bugs or security risks were introduced in the changes.

Quick Start

Run a full code review on all staged changes to identify potential issues.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I automate code review for security and permissions in a Git repository?

Automated code review analyzes Git diffs to detect security vulnerabilities and permission issues. It evaluates staged or committed changes to provide actionable fix plans and severity assessments for identified threats.

What does a comprehensive code review check for beyond standard linting?

A comprehensive code review checks for project-specific architectural concerns like i18n gaps, Firestore index needs, API alignment, and breaking changes that standard linters typically miss.

How do I run a code review on staged Git changes before merging?

To run a code review on staged changes, analyze the diff against the staged scope. The review will identify bugs, quality issues, and platform-specific concerns across web, iOS, Android, and API layers.

Can I check for API alignment and breaking changes across web and mobile platforms?

Yes, multi-platform code review analyzes API alignment and breaking changes across web, iOS, and Android platforms. It verifies that changes in the Git diff do not disrupt existing API contracts.

Does the code review analysis support checking specific Git commit scopes?

Yes, code review analysis supports checking specific Git commit scopes. You can analyze diffs from staged changes, an entire branch, or an individual commit to target the review precisely.

Why does my automated code review flag missing Firestore indexes?

Automated code review flags missing Firestore indexes to prevent runtime query failures. It detects database query patterns within the code diff and validates them against required index configurations.