privacy-guard
Enforces zero-tolerance scanning for PII, secrets, and unauthorized file types before code processing.
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.
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.