Total 30,744 skills, Code Quality has 1622 skills
Showing 12 of 1622 skills
Audit and refactor code for clarity, maintainability, and correctness. Use when the user asks to refactor, clean up code, reduce complexity, fix code smells, or improve code quality.
Audit project directory structure for colocation, grouping, and anti-patterns. Use when creating files, organising components, or deciding where code should live.
Audit and fix filename and naming conventions for consistency. Use when reviewing file names, component names, or export naming across the codebase.
Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Code review skill for analyzing code quality, detecting bugs, and ensuring best practices. Provides comprehensive code review with actionable feedback. Use proactively when user requests code review, quality check, or bug detection. Triggers: code review, review code, check code, analyze code, bug detection, 코드 리뷰, 코드 검토, 버그 검사, コードレビュー, バグ検出, 代码审查, 代码检查, revisión de código, revisar código, detección de errores, revue de code, réviser le code, détection de bugs, Code-Review, Code überprüfen, Fehlererkennung, revisione del codice, rivedere codice, rilevamento bug Do NOT use for: design document creation, deployment tasks, or gap analysis (use phase-8-review).
Review code changes from multiple specialist perspectives in parallel. Use when you want a thorough review of a PR, branch, or set of changes covering security, performance, correctness, edge cases, and ripple effects. Spawns parallel reviewer agents that each focus on a different lens, then synthesizes into a unified review.
Align spec files with implementation. Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code. Use when both a spec file and its implementation are in context.
Use when requesting code review, receiving code review feedback, before merging, or when handling reviewer suggestions - covers both giving and receiving review
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
Automatically scan and execute all skills ending with best-practice to check if the project complies with best practices. Ensure all relevant best practices are checked through the auto-discovery mechanism, and enforce standardized validation instructions to improve output stability.
Batch check whether Skills comply with best practice specifications; automatically verify dimensions such as naming, preface section, structure, file cleanup, and dependencies; support single or batch checks; generate detailed inspection reports; suitable for quality verification after Skill development is completed