frontend-code-review

Review frontend code files for quality and performance checklist violations.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill frontend-code-review-jaydubya818
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-code-review
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/frontend-code-review
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill frontend-code-review-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review frontend code files to identify violations of the code quality and performance checklists, supporting both pending-change and file-targeted reviews to keep projects compliant.

Core Features & Use Cases

  • Automatically inspect frontend files (.tsx, .ts, .js) for naming, memoization, and styling patterns.
  • Support pending-change reviews by flagging checklist violations before commits.
  • Enable file-targeted reviews for specific files and report findings with categorized issues.

Quick Start

Use this skill to initiate a frontend code review on the current project workspace and generate a structured report.

Frequently Asked Questions about frontend-code-review

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

FAQPage Schema
How do I review frontend code quality before committing changes?

Review frontend code quality before committing by inspecting pending changes to flag checklist violations. This process identifies naming, memoization, and styling pattern issues in staged files, generating structured feedback with urgent issue flagging.

What does a frontend code review checklist cover for TypeScript and JavaScript files?

A frontend code review checklist covers naming conventions, memoization patterns, and styling rules for TypeScript and JavaScript files. It inspects .tsx, .ts, and .js files to identify performance and quality violations, categorizing findings for audit-ready reviews.

Can I run a code review on specific .tsx or .ts files instead of all pending changes?

Yes, you can run file-targeted reviews on specific .tsx or .ts files. This targets individual frontend files rather than all staged pending changes, reporting categorized findings and flagging urgent issues for those specific files.

What is the best way to identify memoization and styling violations in React components?

The best way to identify memoization and styling violations in React components is automated checklist inspection of .tsx files. This flags performance issues and non-compliant patterns, providing categorized feedback to keep projects compliant.

Does this code review process support both staged changes and individual file inspections?

Yes, the code review process supports both pending-change reviews for staged changes and file-targeted reviews for specific frontend files. It satisfies structured feedback with urgent issue flagging and categorized findings for both scopes.