skills.rest
kasiopeiya
kasiopeiyaCOMMUNITY
Explore all skills by this author →
GitHub

review

Review TypeScript backend and frontend code with structured reports.

1|Updated Jan 18, 2026
Search Tags:#automation#typescript#frontend#backend#static-analysis#quality-assurance#code-review
One-click install
npx skills add https://github.com/kasiopeiya/oidc-learning-sandbox --skill review-kasiopeiya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/kasiopeiya/oidc-learning-sandbox/tree/main/.claude/skills/review
Command: npx skills add https://github.com/kasiopeiya/oidc-learning-sandbox --skill review-kasiopeiya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams face slow, manual, and inconsistent reviews of TypeScript backend and frontend code, leading to bugs, anti-patterns, and longer release cycles. This skill automates a structured review process to detect issues early and improve code quality across the full stack.

Core Features & Use Cases

  • Automated static review: scans backend/src//*.ts (excluding tests and infrastructure) and frontend/src//*.tsx (excluding tests) to surface issues in handlers, utilities, pages, and contexts.
  • Multi-stage evaluation: categorizes files by type (Backend Handler, Backend Utility, Frontend Page, Frontend Context, Frontend Utility) and applies standardized review criteria.
  • Report-driven workflow: generates a structured review report with findings, suggested improvements, and actionable next steps for developers.

Quick Start

Run the review skill on your TypeScript project to generate a comprehensive code review report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate TypeScript code review for frontend and backend code?▼

Automated TypeScript code review scans monorepo backend and frontend source directories to classify handlers, utilities, pages, and contexts, then applies standardized quality checks to produce a structured report.

What types of TypeScript files are included in automated static analysis?▼

Static analysis targets backend handlers and utilities alongside frontend pages, contexts, and utilities, while explicitly excluding test files and infrastructure scripts to focus on core application logic.

Does automated code review work with TypeScript monorepo projects?▼

Yes, automated code review is designed for TypeScript monorepo projects containing both backend and frontend code, utilizing interactive file selection and deterministic behavior to evaluate multiple packages safely.

How does type-based classification improve code quality assurance?▼

Type-based classification improves quality assurance by categorizing files into distinct roles like Backend Handler or Frontend Page, allowing the review to apply standardized criteria specific to each file type's expected patterns.

What are the limitations of automated TypeScript static analysis?▼

A key limitation is that automated static analysis excludes test files and infrastructure scripts from review, and it is specifically restricted to TypeScript monorepo projects with standard backend and frontend directory structures.

Related Skills

Explore More Software Engineering Skills→
feraudetferaudet

test-conventions

Standardize TypeScript monorepo test conventions with Vitest and React Testing Library.

Community
Intermediate
NimbalystNimbalyst
25

branch-reviewer

Review git branch changes for security, performance, and compatibility issues.

Official
Advanced
jacobcyjacobcy
6

vibe-test-runner

Run four-layer validation with Serena impact analysis, zsh, ShellCheck, bats, and review gating.

Community
Advanced
DaBigHomieDaBigHomie
1

scrutinize

Review codebases for logic errors, security vulnerabilities, and edge cases.

Community
Advanced