security-quality-guard

Audit React/Next.js codebases for linting, security, and TypeScript issues.

Updated Aug 27, 2026

Search Tags:#code quality #typescript #linting #security #authentication #next.js #biome

Ready to run

npx skills add https://github.com/0mar2090/hotelchavin --skill security-quality-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-quality-guard
Source: https://github.com/0mar2090/hotelchavin/tree/main/.agents/skills/security-quality-guard
Command: npx skills add https://github.com/0mar2090/hotelchavin --skill security-quality-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures your React/Next.js codebase is clean, secure, and maintainable by enforcing strict linting, robust authentication, and comprehensive TypeScript practices.

Core Features & Use Cases

Biome Linting & Formatting: Replaces ESLint/Prettier with Biome for unified code quality.
Robust Authentication: Enforces secure access control using Clerk or Auth.js for sensitive data.
Strict TypeScript: Eliminates any types and promotes type safety with explicit interfaces and strict compiler options.
Absolute Imports: Organizes code structure with clean, alias-based imports.
Use Case: Before merging a new feature, run this Skill to automatically format the code, check for security vulnerabilities in API routes, and ensure all new components are strictly typed, preventing potential bugs and security risks.

Quick Start

Run the security-quality-guard skill to audit the current project for linting, security, and TypeScript issues.

Frequently Asked Questions about security-quality-guard

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

FAQPage Schema

How do I audit a Next.js codebase for security and code quality issues?▼

To audit a React project for linting and security, you run a comprehensive check that formats code with Biome, verifies strict TypeScript typing, and inspects Clerk or Auth.js authentication setups to secure sensitive data and API routes.

What is the best way to enforce strict TypeScript and eliminate any types in React?▼

The best way to enforce strict TypeScript and eliminate any types is by applying strict compiler options alongside explicit interfaces, ensuring all new components are strictly typed to prevent potential bugs in your React codebase.

Does Biome work with Next.js for both linting and formatting?▼

Yes, Biome works with Next.js by replacing ESLint and Prettier to provide a unified code quality solution, handling both linting and formatting to keep your codebase clean and maintainable.

How do I check Clerk authentication security in API routes before merging?▼

Checking Clerk authentication security in API routes involves auditing access control implementations to ensure sensitive data is protected, verifying that robust authentication is enforced before merging new features.

Can I enforce absolute imports in a TypeScript project automatically?▼

Yes, you can enforce absolute imports in a TypeScript project by applying alias-based import configurations, which organizes the code structure and ensures clean import paths across the codebase.

What are the limitations of replacing ESLint with Biome for code quality checks?▼

While replacing ESLint with Biome unifies linting and formatting, limitations may arise if your project relies on highly specific ESLint plugins not yet supported by Biome, requiring adjustments to your code review checklist.