code-reviewer
Code review methodology, severity classification, and quality assessment patterns
Code review methodology, severity classification, and quality assessment patterns
Review PooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
Review skillstash PRs and summarize validation issues
[Code Quality] Establishes test coverage requirements before refactoring. Use to identify missing tests, create minimal safety net tests, and define verification strategy for behavior preservation.
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Use when reviewing large PRs to surface changes requiring human attention
Code quality standards, linting rules, and CI/CD principles.
Review code against spec compliance - checks implementation matches spec requirements, identifies deviations, reports compliance score, triggers evolution if needed
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable
Use to validate spec documents for correctness, completeness, and consistency. Ensures specs follow SuperSpec format and are ready for implementation.
Enforce TypeScript type organization rules. Use when creating types, interfaces, or DTOs. All types MUST go in /types directory - never inline in components.
Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns. Use for PR reviews, pre-commit checks, or branch comparisons.
Conducts comprehensive frontend code reviews including React/Vue/Angular component analysis, TypeScript/JavaScript quality assessment, CSS/styling review, performance optimization, accessibility compliance, security vulnerabilities, and best practices validation. Produces detailed review reports with specific issues, severity ratings, and actionable recommendations. Use when reviewing frontend code, analyzing React/Vue/Angular components, checking JavaScript/TypeScript quality, validating CSS/SCSS, assessing web performance, or when users mention "review frontend code", "check React components", "analyze JavaScript", "review TypeScript", "validate accessibility", or "frontend code quality".
Guide for security tooling (analyzers, fuzzers, decompilers, compilers) and consistent placement in README.md.
Import conventions and ordering rules. Use when writing imports or organizing import statements. Enforces explicit named imports, never wildcards.
Skill para revisar codigo com checklist de qualidade
Automatically fix ESLint errors by modifying code to comply with linting rules. For small codebases (≤20 errors), fixes directly. For larger codebases (>20 errors), spawns parallel agents per directory for efficient processing. Never disables rules or adds ignore comments.
Comprehensive code review guidelines for React 19 TypeScript projects
C++23 best practices with Google Test 1.15, clang-format 19, and modern C++ standards.
Senior Frontend Code Reviewer with 12+ years JavaScript/TypeScript experience. Use when reviewing React/TypeScript code, checking code quality and style, verifying accessibility compliance, ensuring test coverage, or configuring linting tools (ESLint, Prettier).
Python coding standards for Amplifier including type hints, async patterns, error handling, and formatting. Use when writing Python code for Amplifier modules.
Python code quality with ruff (linting & formatting) and mypy (type checking). Covers pyproject.toml configuration, pre-commit hooks, and type hints. Use when user mentions ruff, mypy, linting, formatting, type checking, code style, or Python code quality.
Validates PHP test files for CakePHP projects, ensuring compliance with testing standards including proper documentation format, Configure::read usage, and avoiding prohibited patterns
Review methodology for code changes with confidence scoring.