review-code-quality

Analyze source code for TypeScript strictness, naming conventions, and OXC linting compliance.

18|4|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/louisbrulenaudet/monorepo-template --skill review-code-quality-louisbrulenaudet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code-quality
Source: https://github.com/louisbrulenaudet/monorepo-template/tree/main/.agents/skills/review-code-quality
Command: npx skills add https://github.com/louisbrulenaudet/monorepo-template --skill review-code-quality-louisbrulenaudet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses technical debt and inconsistency by automating the review of code against strict project standards, ensuring maintainability and reliability across the monorepo.

Core Features & Use Cases

  • Standards Enforcement: Validates naming conventions, TypeScript strictness, and OXC linting/formatting rules.
  • Architecture Review: Checks for proper separation of concerns, DRY principles, and correct error handling patterns.
  • Use Case: Before merging a pull request, use this Skill to identify violations of the project's TypeScript strict mode or naming conventions, ensuring the codebase remains clean and scalable.

Quick Start

Use the review-code-quality skill to perform a full codebase audit of the current repository.

Frequently Asked Questions about review-code-quality

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

FAQPage Schema
How do I automate TypeScript strict mode and naming convention checks before a pull request?

Automated code quality review validates TypeScript strict mode and naming conventions by analyzing source code against monorepo standards, catching technical debt and formatting inconsistencies before pull request merging.

What is the best way to identify technical debt and code duplication across a monorepo?

Performing a full codebase audit identifies technical debt and code duplication across apps and shared packages by validating architectural patterns, DRY principles, and separation of concerns defined within the monorepo.

Can I validate OXC linting rules and error handling patterns automatically?

Yes, automated code quality validation checks compliance with OXC linting rules and error handling best practices to ensure production-grade code quality and maintainability across the monorepo.

Does automated code review work with shared packages in a monorepo architecture?

Automated code review specifically targets apps and shared packages within a monorepo, validating architectural patterns and separation of concerns to ensure codebase scalability and consistency across distributed modules.

How does static analysis enforce separation of concerns and DRY principles?

Static analysis reviews source code for proper separation of concerns and DRY principles by checking architectural patterns defined in the monorepo, targeting technical debt and duplication to maintain production-grade quality.

Why does technical debt accumulate in TypeScript monorepos despite linting?

Technical debt accumulates when linting alone cannot validate architectural patterns, DRY principles, and error handling best practices, requiring automated code quality review to ensure maintainability and reliability across the monorepo.