code-review

Analyze PR diffs for SEO, i18n, security, and Angular quality risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes the current pull request diff against the base branch to identify SEO risks, i18n desync, Angular quality issues, and exposed credentials, producing a structured risk report.

Core Features & Use Cases

  • Diff analysis: Automatically detects changes between the PR and the base branch to surface high-risk areas.
  • Risk classification: Categorizes findings by severity (critical, high, medium, low) across SEO, i18n, and security.
  • Actionable report: Generates a structured report suitable for PR reviewers and developers.
  • Use Case: When a PR touches routing or multilingual content, surface risks before merge.

Quick Start

Run the code-review skill on a PR branch to produce a risk report for the current changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I analyze a PR diff to surface SEO and i18n risks?

Analyzing a PR diff against the base branch surfaces SEO risks, i18n desync, Angular quality issues, and exposed credentials by categorizing findings into a structured risk report.

Can I automate code review risk assessment for Angular projects?

Automating code review risk assessment for multi-language Angular projects involves analyzing PR diffs against the base branch to detect routing and multilingual content risks before merging.

Does this code review tool support multi-language i18n desync detection?

This code review tool supports multi-language Angular projects by identifying i18n desync risks and categorizing findings by severity to generate an actionable report for developers.

How are security and quality findings classified in the generated report?

Security and quality findings are classified by severity levels including critical, high, medium, and low, covering SEO, i18n, and security to surface high-risk areas in the generated report.

What is the best way to detect exposed credentials in a pull request?

Analyzing the PR diff against the base branch detects exposed credentials by surfacing security risks and generating a structured risk report for PR reviewers and developers.