Total 54,063 skills, Code Quality has 2437 skills
Showing 12 of 2437 skills
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
A comprehensive verification system for Claude Code sessions.
Guides testing and code quality for kcli. Use when writing tests, running linting, or validating changes before committing.
Guide for using ty, the extremely fast Python type checker and language server. Use this when type checking Python code or setting up type checking in Python projects.
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Use when receiving code review feedback, processing PR comments, or needing to evaluate suggestions before implementing - requires technical verification not blind agreement
Use when deciding where to catch errors. Use when errors propagate too far or not far enough. Use when designing component/service isolation.
General coding best practices and software engineering principles to build robust, maintainable, and scalable software.
Expert at diagnosing and fixing performance bottlenecks across the stack. Covers Core Web Vitals, database optimization, caching strategies, bundle optimization, and performance monitoring. Knows when to measure vs optimize. Use when "slow page load, performance optimization, core web vitals, bundle size, lighthouse score, database slow, memory leak, optimize performance, speed up, reduce load time, performance, optimization, core-web-vitals, caching, profiling, bundle-size, database" mentioned.
The Essentialist. Ruthlessly simplifying code, removing dead features, and enforcing Clean Architecture.
Standardized output format for code reviews with severity labels, file:line references, and fix code snippets. Use when generating review reports that need consistent, actionable feedback structure.
Apply factory function patterns to compose clients and services with proper separation of concerns. Use when creating functions that depend on external clients, wrapping resources with domain-specific methods, or refactoring code that mixes client/service/method options together.