code-review

Review Photo Map MVP code for security, architecture, and MVP scope compliance.

2|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/kojder/photo-map-app --skill code-review-kojder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kojder/photo-map-app/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/kojder/photo-map-app --skill code-review-kojder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps review, analyze, and inspect code for the Photo Map MVP project, focusing on security, performance, naming, testing, and MVP scope compliance.

Core Features & Use Cases

  • Read-Only Analysis: Inspect Java and TypeScript files for best practices.
  • Quality & Security: Identify security issues, architecture violations, and missing tests.
  • Decision Support: Surface actionable recommendations during pull request reviews.

Quick Start

Query Claude Code Review to audit the latest PR and surface findings across security, architecture, and test coverage, with concrete examples.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review Java and TypeScript code for security issues during pull requests?

Code review analyzes Java and TypeScript files for security vulnerabilities, architecture violations, and best practices. It surfaces actionable findings via comments, examining patterns like DTO usage, transactional boundaries, and security compliance without editing the codebase.

What security patterns and naming conventions does code review enforce?

Code review enforces security patterns, DTO usage, transactional boundaries, English naming standards, and MVP scope compliance. It validates Git commit and PR standards while identifying architecture violations and missing tests across Photo Map MVP projects.

Can I use code review to audit existing pull requests and identify test coverage gaps?

Yes. Code review performs read-only audits of pull requests to surface test coverage gaps, security issues, and architecture violations. It produces findings across quality, security, and testing dimensions using read-only inspection of file content.

How does code review work with Java and TypeScript files in the same project?

Code review inspects both Java and TypeScript files within Photo Map MVP projects, applying consistent security, architecture, and naming standards across the codebase. It uses read-only analysis via content inspection and pattern matching without modifying files.

What's the difference between code review and automated linting tools?

Code review performs architectural and security audits with contextual analysis of patterns like DTO usage and transactional boundaries, whereas linters focus on syntax and style. It surfaces business logic violations and MVP scope compliance that generic linting cannot detect.

When should I run code review in my development workflow?

Run code review during pre-commit reviews, pull-request audits, bug investigations, and refactoring assessments. It's designed for Photo Map MVP projects to verify security, architecture compliance, and test coverage before merging changes.