Total 53,816 skills, Code Quality has 2426 skills
Showing 12 of 2426 skills
Expertise in analyzing time-series repository health metrics, investigating root causes, and proposing proactive workflow improvements.
Review asynchronous Python code to identify race conditions, deadlocks, and inefficient patterns. Use when working with asyncio, aiohttp, or FastAPI.
Use to review uncommitted changes and recent commits in the working tree. Dispatches 8 specialized review agents in parallel and returns a consolidated report
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
Use when the user asks for a broad codebase review, substantial PR/branch review, architecture audit, tech-debt scan, cleanup assessment, structural sanity check, or design-alignment review. Default workflow: use sub-agents when available unless specifically forbidden; do not require the user to mention sub-agents, council mode, delegation, or parallel review. Focus on cruft, duplication, weak boundaries, missed reuse, lifecycle/concurrency risks, test/roadmap drift, and code aesthetics. Do not use for narrow bug fixes, ordinary small-diff reviews, frontend visual QA, repo-onboarding docs, or OpenAI Agents SDK production-readiness review. Output evidence-backed findings first, then pressure points, design alignment, open questions, and follow-through.
Walk the user through a PR as a single top-to-bottom narrative ordered by dependency/causal flow, with a heavy scrutiny pass for bugs, missing tests, scope creep, and security. Operates on a temp git worktree so it works while the main working tree is dirty. Use when the user asks to review a PR, walk through a PR, review a PR, or review one branch against another.
Use when coding standards, security patterns, or project conventions need to be discovered before implementation begins.
4-phase root cause debugging: understand bugs before fixing.
Review PRs: diffs, inline comments via gh or REST.
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Four LLM reviewers challenge changes from independent angles.
Provides comprehensive code review covering 6 focused aspects - architecture & design, code quality, security & dependencies, performance & scalability, testing coverage, and documentation & API design. Use this skill for deep analysis with actionable feedback after significant code changes.
Activate when creating new modules, refactoring class hierarchies, introducing design patterns, or making changes spanning 3+ files in the APM CLI codebase.