code-review-skill

Automate code review guidance for multi-tenant SaaS projects with tenant isolation.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/boparaiamrit/build-second-brain --skill code-review-skill-boparaiamrit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-skill
Source: https://github.com/boparaiamrit/build-second-brain/tree/main/plugins/build-second-brain/skills/code-review-skill
Command: npx skills add https://github.com/boparaiamrit/build-second-brain --skill code-review-skill-boparaiamrit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exhaustive code review checklist for multi-tenant SaaS covering backend (NestJS), frontend (Next.js/React), security, performance, multi-tenancy, and MSSP compliance. Provides PR review templates, code smell detection, and severity-based feedback.

Core Features & Use Cases

  • Enforces tenant hierarchy (Company > Workspace > Domain) on every review
  • Provides a structured 3-read approach and a consistent review order
  • Includes templates for PR comments and breach/quality risk explanations
  • Used when reviewing PRs across UC1, UC2, and UC3 to maintain cross-tenant safety

Quick Start

Review a PR by following the included checklist and templates to generate structured, actionable feedback.

Frequently Asked Questions about code-review-skill

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

FAQPage Schema
How do I automate code review checklists for multi-tenant SaaS PRs?

Multi-tenant SaaS code review checklists are automated by applying structured templates that enforce tenant isolation, verify governance across NestJS and Next.js, and generate severity-based PR feedback.

What is tenant isolation governance in a multi-tenant SaaS code review?

Tenant isolation governance in a multi-tenant SaaS code review ensures strict boundaries across the Company, Workspace, and Domain hierarchy, preventing cross-tenant data breaches and maintaining MSSP compliance.

How do I enforce a consistent review order for NestJS and Next.js pull requests?

A consistent review order for NestJS and Next.js pull requests is enforced by following a structured 3-read approach with standardized templates, ensuring backend, frontend, security, and multi-tenancy checks are evaluated systematically.

Can I use these code review templates across different multi-tenant SaaS deployments?

You can use these code review templates across UC1, UC2, and UC3 multi-tenant SaaS deployments, providing reusable checklists and audit-ready comments that scale across various cross-tenant safety requirements.

What is the best way to generate audit-ready PR comments for MSSP compliance?

The best way to generate audit-ready PR comments for MSSP compliance is using standardized templates that provide severity-based feedback and structured breach explanations during the code review process.

What limitations exist when detecting code smells in multi-tenant SaaS projects?

Code smell detection in multi-tenant SaaS projects relies on applying the provided checklist and templates during PR reviews, focusing specifically on tenant hierarchy enforcement and cross-tenant safety rather than general architectural refactoring.