comment-analyzer
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
[Design System] Validate that code and styles use official design tokens instead of hard-coded values. Use when (1) reviewing CSS/SCSS/Tailwind/styled-components for hard-coded colors/spacing, (2) checking SwiftUI/UIKit for raw color/font values, (3) auditing Unity styles for magic numbers, (4) enforcing design system compliance, (5) user asks to 'check design tokens', 'validate tokens', 'find hard-coded values', or 'audit design system usage'.
Linter-driven refactoring patterns to reduce complexity and improve code quality. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Applies storifying, type extraction, and function extraction patterns.
Basedpyright static type checker configuration, installation, and usage patterns. Use when implementing type checking, configuring LSP, comparing type checkers, or setting up strict type validation in Python projects. Triggered by: basedpyright, pyright, type checking, LSP, mypy alternative, static analysis.
Guide for conducting thorough code reviews focusing on correctness, security, performance, maintainability, and best practices
Calculate code quality metrics - complexity, coverage, maintainability
Use when running verification pipelines, checking test/lint/type status, or ensuring code quality gates pass before completing work
Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration
Validate markdown documentation files for formatting issues, syntax errors, broken links, and quality standards. Use when checking .md files for compliance with documentation standards or after editing markdown files.
Enforces zero-tolerance scanning for PII, secrets, and unauthorized file types before code processing.
Plugin validation errors and fixes
Linter-driven refactoring patterns to reduce complexity and improve code quality in React/TypeScript. Use when ESLint fails with SonarJS complexity issues (cognitive, cyclomatic, expression) or when code feels hard to read/maintain. Applies component extraction, hook extraction, and simplification patterns.
Critical Code Reviewer. Focuses on security, performance (Big O), and strict typing.
Nature-Spotsプロジェクトのコーディング規約。命名規則、禁止パターン、インポート順序、コメント基準を定義します。コードレビュー時に自動参照されます。
Analyze design system usage, identify inconsistencies across patterns, generate fixes, and maintain visual coherence with automated style guide generation
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
PHP coding standards (PSR-12, PHPDoc, type hints) for any PHP project
C++ coding conventions. Use when editing .cpp/.hpp files or asking about C++ style.
Load PR comments and feedback for code review. Use when the user wants to see reviewer feedback, check for unresolved comments, understand what changes are requested, or review discussion on a PR.
Vulture and deadcode tools for detecting unused Python code (functions, classes, variables, imports). Use when cleaning up codebases, removing unused code, or enforcing code hygiene in CI. Triggered by: vulture, deadcode, dead code detection, unused code, code cleanup, remove unused.
Validates PopKit compliance with Claude Code patterns using concrete standards and automated checks
Ruby 3.4+ best practices with RSpec 4, RuboCop 2, Bundler, and Rails 8 patterns.
Code quality guidelines. ALWAYS use skill for ANY code changes.