Total 50,474 skills, Code Quality has 2287 skills
Showing 12 of 2287 skills
High-performance Rust optimization. Profiling, benchmarking, SIMD, memory optimization, and zero-copy techniques. Focuses on measurable improvements with evidence-based optimization.
Use when receiving code review feedback, processing PR comments, or needing to evaluate suggestions before implementing - requires technical verification not blind agreement
Audit and refactor code for clarity, maintainability, and correctness. Use when the user asks to refactor, clean up code, reduce complexity, fix code smells, or improve code quality.
Audit and fix filename and naming conventions for consistency. Use when reviewing file names, component names, or export naming across the codebase.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Code review skill for analyzing code quality, detecting bugs, and ensuring best practices. Provides comprehensive code review with actionable feedback. Use proactively when user requests code review, quality check, or bug detection. Triggers: code review, review code, check code, analyze code, bug detection, 코드 리뷰, 코드 검토, 버그 검사, コードレビュー, バグ検出, 代码审查, 代码检查, revisión de código, revisar código, detección de errores, revue de code, réviser le code, détection de bugs, Code-Review, Code überprüfen, Fehlererkennung, revisione del codice, rivedere codice, rilevamento bug Do NOT use for: design document creation, deployment tasks, or gap analysis (use phase-8-review).
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Use when requesting code review, receiving code review feedback, before merging, or when handling reviewer suggestions - covers both giving and receiving review
Identify CPU and memory bottlenecks in Python code using cProfile or memory_profiler. Use to optimize mission-critical Python services.
Orchestrate parallel debugging agents with root-cause tracing for multi-failure scenarios
Use when writing type annotations on variables. Use when TypeScript can infer the type. Use when code feels cluttered with types.
Simplify code and remove legacy/backcompat shims while preserving behavior. Use when asked to clean up or simplify code.