review

Review TypeScript/React and C# pull requests for code quality, design, performance, tests, and documentation.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/yasudaProduct/chord-chart --skill review-yasudaproduct
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/yasudaProduct/chord-chart/tree/main/.claude/skills/review
Command: npx skills add https://github.com/yasudaProduct/chord-chart --skill review-yasudaproduct

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review workflows often lack a consistent, thorough checklist, leading to missed issues and inconsistent quality across PRs. This guide provides structured, repeatable review criteria to elevate code quality for both frontend and backend codebases.

Core Features & Use Cases

  • Provides clear evaluation criteria for TypeScript/React frontend code and C# backend code, including code quality, architecture, performance, tests, and documentation.
  • Serves as a reusable checklist for PRs, onboarding new reviewers, and enforcing coding standards across teams.
  • Use Case: A reviewer applies the checklist to a pull request to ensure proper typing, clean architecture, proper error handling, and adequate tests.

Quick Start

Review the latest pull request using this guide to assess code quality, architecture, performance, and tests.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for TypeScript and React frontend code?

To review a pull request for TypeScript and React frontend code, evaluate proper typing, component architecture, performance, and test coverage using structured criteria to ensure maintainability and reliability.

What should a C# backend code review checklist include?

A C# backend code review checklist should include architecture adherence, error handling, code quality, performance, and test coverage to maintain reliable and structured backend project standards.

What is the best way to enforce coding standards during pull requests?

The best way to enforce coding standards during pull requests is applying a structured, repeatable checklist that covers design, tests, and documentation for both frontend and backend codebases.

How do I ensure proper typing and architecture adherence in a PR?

To ensure proper typing and architecture adherence in a PR, apply structured review guidelines that enforce specific checks for TypeScript types and architectural rules across the codebase.

Can I use a code review checklist for onboarding new reviewers?

Yes, you can use a structured code review checklist for onboarding new reviewers by providing clear, repeatable evaluation criteria for code quality, architecture, and tests across PR scenarios.

Why does my code review workflow miss issues across different pull requests?

Your code review workflow misses issues across pull requests because it lacks a consistent, thorough checklist, which leads to inconsistent quality evaluation across frontend and backend codebases.