Total 54,018 skills, Code Quality has 2434 skills
Showing 12 of 2434 skills
Code quality checks, formatting, and metrics via qlty CLI
Review code through hostile perspectives to find bugs, security issues, and unintended consequences the author missed. Use when reviewing PRs, auditing codebases, or before critical deployments.
Continuously steers the codebase toward the VISION.md. Reads the vision, assesses current state, picks the highest-impact next action, builds with TDD, commits, and repeats. Never stops. Use when you want autonomous, vision-driven development.
Review code for quality, security, and pattern compliance, then auto-fix Critical/High issues. Grounds every finding in actual codebase reference files.
Code Reviewer Specialist. Use this to review PRs, check security, and ensure code quality standards before merging.
Development best practices and project patterns. Use when starting projects, setting up CLAUDE.md, coding TypeScript/Next.js/React/Supabase, implementing AI flows, data fetching, testing, deployment, git workflows, browser automation, centralized configuration, or Tailwind CSS v4.
Build verification, error recovery, and application of review fixes. Use this when the user mentions build verification, error recovery, applying review fixes, test failures, lint errors, or CI breaks. Do NOT load this for: implementation work, reviews, setup, or new feature development.
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", or "technical debt". Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", or "readable code". Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.
Review and refactor code in your project according to defined instructions
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
Scan and analyze a software repository or project for design quality using principles from A Philosophy of Software Design by John Ousterhout. Use when user asks to review, audit, scan, or evaluate code quality, design quality, architecture, or technical debt. Also trigger for: code review, design review, complexity analysis, code health check, module depth analysis, information hiding review, how good is my code, review my project, find design problems, what is wrong with my codebase, rate my code, or anything about evaluating software design quality at a structural level. This is not a linter or style checker. It evaluates deep design qualities like module depth, abstraction quality, information hiding, and complexity patterns.