code-review

Name: code-review
Availability: InStock
Author: mockly

Classifies Git changes as front/back-end and generates reviewable reports.

Updated Aug 23, 2026

Search Tags:#automation #security #frontend #backend #quality #code-review

Ready to run

npx skills add https://github.com/Mockly-Company/mockly-mobile --skill code-review-mockly-company

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Mockly-Company/mockly-mobile/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Mockly-Company/mockly-mobile --skill code-review-mockly-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the code review process by analyzing frontend and backend changes, helping teams maintain consistency, catch issues early, and reduce review time.

Core Features & Use Cases

Frontend/Backend separation: Detects whether modified files are frontend or backend.
Perspective-based review guides: References to frontend-review-guide.md or backend-review-guide.md depending on the code.
Common quality checks: Evaluates code quality, security, tests, typing safety, and performance.
Practical feedback: Provides concrete feedback formats with examples.

Quick Start

Call the skill with a description of your changes or a git diff, for example: "code-review" to trigger the review.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code reviews for frontend and backend changes?▼

Code review automation classifies your git changes by file type and applies domain-specific review criteria to each. It detects frontend versus backend modifications, references the appropriate review guide, and generates structured feedback with severity levels and code examples ready for integration.

Can I use automated code reviews to enforce security and quality standards?▼

Yes. Automated code review evaluates quality, security, tests, typing safety, and performance against staged and unstaged git changes. It applies both frontend and backend best practices, flagging issues with concrete examples and severity ratings for consistent enforcement across your codebase.

What's the best way to catch frontend and backend issues in the same review?▼

Perspective-based review separates frontend and backend concerns by automatically detecting file types and directories, then applying distinct review guidance to each. This eliminates context switching and ensures domain-specific quality checks reach the right reviewers without manual categorization.

How does automated code review integrate with RAG pipelines?▼

The skill generates structured, report-ready feedback including file-level summaries, issue severities, code examples, and best practices formatted for RAG system ingestion. This enables semantic retrieval and contextual integration into downstream analysis or knowledge systems.

Do I need to manually categorize code changes as frontend or backend?▼

No. Automated code review detects frontend and backend file types by extension and directory structure, eliminating manual classification. It applies the appropriate review guidance automatically based on what changed.

What information does automated code review provide beyond flagged issues?▼

Beyond issue detection, it delivers file-level summaries, severity classifications, concrete code examples, and domain-specific best practices. Output is structured for report generation and systems integration, reducing review time while maintaining consistency.