Total 50,341 skills, Code Quality has 2286 skills
Showing 12 of 2286 skills
Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.
Review pull requests. Use when user asks to "review a PR", "/review-pr", or wants to review a pull request.
Implements and enforces code quality gates for TypeScript/React projects. Use when setting up Biome/ESLint/TypeScript, configuring pre-commit hooks (Husky), fixing lint errors, or running quality checks. Examples - "setup code quality", "fix lint errors", "configure Biome", "run quality checks".
Enforce Pythonic standards using Black, Isort, and Flake8. Use to ensure consistency across large Python codebases and team environments.
Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
ANTI-PATTERN - Example showing violations of self-containment (DO NOT COPY)
Review Prisma code for common violations, security issues, and performance anti-patterns found in AI coding agent stress testing. Use when reviewing Prisma Client usage, database operations, or performing code reviews on projects using Prisma ORM.
Review code changes in a feature branch before merging. Use when asked to review a branch, review changes, check a PR, or audit code before merge. Compares the current branch against the default branch (main/master) and categorizes issues by severity (Critical, Major, Minor) with actionable solutions.
Performs comprehensive PR code review from 5 perspectives (quality/performance/tests/docs/security) in parallel, providing Blockers/Suggestions/Nice-to-have and merge decision. Args: /review [owner/repo] [pr-number] [--focus all|security|perf|qa|docs|types] Activates when user mentions "review", "PR確認", "コードレビュー", "マージ判定".
Detect and refactor code duplication with PMD CPD. TRIGGERS - code clones, DRY violations, duplicate code.
Function design patterns emphasizing single responsibility and clarity.
Dynamically validate that the implemented codebase matches architectural decisions documented in plan files. Use when validating implementation matches planning documents, checking for architecture drift, or preparing for architecture reviews.