Enforce evidence-based completion claims with actual command output. Use before (1) claiming tests pass, (2) claiming a bug is fixed, (3) claiming a task completed successfully, (4) claiming performance improved, (5) saying "ready for review". Prevents phrases like "should pass" or "that should fix it" - requires fresh verification evidence.
Apply fixes to entities/components with best practice validation. Searches library docs for simpler patterns, checks for built-in features, validates fixes maintain performance and architectural integrity. Integrates with breath-synchronization skill for breathing-related fixes. Works with parameter tuning, library pattern replacement, and performance optimization.
Comprehensive code review for pull requests with quality, security, and best practices analysis
ESLint, Prettier, and StyleLint configuration standards for JavaScript code quality and formatting, including flat config setup, rule management, and build integration
Prevents "lazy" coding habits by enforcing full implementation and banning placeholders.
Review changes to find high-impact bugs or regressions. Use for code review of local changes or pull requests.
業界のベストプラクティスとアーキテクチャ標準に照らしてTerraformコードをレビューします。ユーザーがコードレビュー、ベストプラクティスのアドバイス、またはアーキテクチャの改善を求めた場合に使用してください。
Coding conventions and best practices for TypeScript, React 19, and Next.js 15. Use when writing new code, reviewing code quality, or ensuring consistency with Airbnb style guides and project-specific patterns.
コード品質レビュー - アーキテクチャ、コード臭、パフォーマンス、型安全性を統合評価
Write quality content for HTML documents. Use when writing text content, prose, descriptions, or any human-readable content in HTML files. Ensures spelling and style quality.
Guide for fixing Python strict type checking errors (Pylance/MyPy). Use this skill when resolving unknown type, missing import, or type mismatch errors in Python files. Covers common patterns for TypedDict, generics, casting, and protocol alignment.
Detect spaghetti code and propose specific refactoring solutions. Analyzes detected issues and provides concrete code improvements.
Pre-implementation validation framework requiring ≥90% confidence before coding. Prevents wrong-direction work by assessing duplicates, architecture alignment, documentation, OSS references, and root cause understanding. Use before implementing features, fixes, or refactoring to save 5K-50K tokens per prevented error.
Generic code review for test code. Use as part of parallel test review execution.
Format code using dotnet format, prettier, and other formatting tools. Use when task involves code style fixes, formatting consistency, or preparing code for commit.
Guidance for writing valid Emacs Lisp code with incremental validation. Use when writing or modifying elisp functions, especially complex nested forms with cl-loop, multiple let* bindings, or lambdas.
代码审核导航。触发：用户通知"编译通过"或"请审核代码"时使用；对子代理产出的代码进行质量审核、规范检查、越界检查，输出审核报告。
Review code changes and remove AI-generated patterns like excessive comments, gratuitous defensive checks, type escape hatches, and over-engineering.
Enforce the "Premium" aesthetic and accessibility standards.
