Total 30,695 skills, Code Quality has 1621 skills
Showing 12 of 1621 skills
Use when defining or evolving public interfaces, schema boundaries, or pydantic usage in Python. Also use when annotations are missing on public APIs, pydantic models appear everywhere instead of at trust boundaries, contract changes lack migration guidance, or Any/object types are overused across module boundaries.
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
Use when component does too many things. Use when mixing data fetching, logic, and presentation. Use when code is hard to test.
This skill processes unresolved GitHub PR review discussions. Activated when the user provides a GitHub PR link (github.com/.../pull/...) or mentions "PR review", "review PR", "process review comments", etc.
Use when preparing branches, commits, or PRs for Python changes — scoping work, running validation gates, and ensuring merge readiness. Also use when debugging CI gate failures, resolving lockfile conflicts, or uncertain what checks to run before opening a PR.
Intelligent Code Debugging Assistant that helps you visualize how your code runs. When you say things like "I want to see why this function is so slow", "The code throws an error halfway through execution and I don't know where the problem is", or "This business logic is too complex and I can't figure out the execution order", I will help you trace the code execution path, identify slow-performing sections, and locate the root cause of errors. When skill optimization points are identified, I will ask if you want to call the skill-evolution-driver for optimization
Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
Help teams continuously improve skills, automatically identify skill optimization opportunities (such as missing essential information, format issues, version update needs, etc.), execute secure update processes (backup, modification, testing, restoration), and ensure skill quality keeps improving as the project progresses
Provides practical guidance for conducting thorough code reviews that identify issues early, promote knowledge sharing, and deliver constructive feedback. This skill should be used when reviewing pull requests, establishing team review standards, or mentoring developers on effective review practices.
Analyzes cyclomatic and cognitive complexity, identifies overly complex functions. Use when assessing code complexity or identifying functions that need simplification.
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
Provides refactoring recommendations and step-by-step improvement plans. Use when planning refactoring, improving code structure, or reducing technical debt.