code-review

Identify code quality issues and enforce project standards in monorepo PR reviews.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/feraudet/ssii --skill code-review-feraudet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/feraudet/ssii/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/feraudet/ssii --skill code-review-feraudet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is essential for quality but often inconsistent; this guide provides a comprehensive, enforceable checklist to standardize reviews across a software project.

Core Features & Use Cases

  • Checklist-driven reviews aligned with the monorepo structure (backend/frontend).
  • Standards for architecture, typing, error handling, security, and performance.
  • Encourages DRY principles and clear naming to improve long-term maintainability.
  • Guides reviewers through common scenarios such as PRs touching Prisma models or Express routes.

Quick Start

Review a pull request by applying the code-review standards checklist provided in this guide.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I standardize code reviews across a monorepo with backend and frontend components?

Standardize monorepo code reviews by applying a structured checklist that validates architecture, typing, error handling, and security across both backend and frontend components. This enforces consistent project standards and DRY principles during pull request approvals.

What should I check when reviewing a pull request that modifies Prisma models or Express routes?

When reviewing PRs touching Prisma models or Express routes, check for typing accuracy, proper error handling, security vulnerabilities, and performance issues. The review process provides clear, actionable guidance for these specific backend scenarios.

Can I use a checklist-driven approach to enforce TypeScript standards during PR reviews?

Yes, you can enforce TypeScript standards during PR reviews using a checklist-driven approach. It validates type safety, architectural boundaries, and naming conventions to improve long-term maintainability across feature branches and commits.

What is the best way to identify code quality issues in feature branches before merging?

Identify code quality issues in feature branches by running structured validation checks for architecture, typing, error handling, security, and performance. This provides reviewers with actionable feedback to ensure adherence to project standards before merging.

Does this code review process work for both frontend and backend commits in a monorepo?

Yes, the code review process works for both frontend and backend commits in a monorepo. It applies standardized validation checks across the entire repository structure to ensure consistent code quality and security adherence.