Total 50,520 skills, Code Quality has 2287 skills
Showing 12 of 2287 skills
Fetch PR feedback from all GitHub sources and validate every comment before acting. Use when user needs to process PR review comments, address reviewer feedback, or triage pull request discussions. Use for "review comments", "PR feedback", "address reviews", "address feedback", or "what did reviewers say". Do NOT use for creating new PRs, code review of local changes, or general code analysis without an existing PR.
Review the code quality of a spec-driven change. Checks readability, security, performance, and best practices before archiving.
Simplify and refine recently modified code while preserving functionality. Use when asked to "deslop", "clean up code", "simplify code", or after making changes that could benefit from refinement.
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm
Build a persistent knowledge graph of your codebase so Claude reads only what matters — up to 49x fewer tokens on coding tasks.
Execute a micro-level React code quality audit. Validates code against live GitHub standards for testing, component architecture, hooks patterns, state management, performance, and TypeScript. Produces a detailed violations report with prioritized action plan. Use when the user asks to check React code quality, validate best practices, or review frontend code standards. Triggers on: 'react best practices', 'react code quality', 'component review', 'hooks review', 'react standards', 'frontend code quality'.
Use when you need to review, improve, or refactor Java code for object-oriented design quality — including applying SOLID, DRY, and YAGNI principles, improving class and interface design, fixing OOP concept misuse (encapsulation, inheritance, polymorphism), identifying and resolving code smells (God Class, Feature Envy, Data Clumps), or improving object creation patterns, method design, and exception handling. Part of the skills-for-java project
Use when you need to add or evaluate Maven dependencies that improve code quality — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), or architecture testing (ArchUnit) — and want a consultative, question-driven approach that adds only what you actually need. Part of the skills-for-java project
Comprehensive code review checklist for Go projects. Evaluates code quality, idiomatic patterns, error handling, naming, package structure, and test coverage. Use when reviewing Go code, PRs, or before merging changes. Trigger examples: "review this code", "check this PR", "code review", "review Go file". Do NOT use for security-specific audits (use go-security-audit) or performance-specific analysis (use go-performance-review).
Force a skeptical second pass on your own work. Because 'it should work' has never once been true.
This skill should be used when the user asks to "audit this codebase", "audit this code", "security audit", "code audit", "find vulnerabilities", "check for bugs", "review code quality", "find dead code", "check for anti-patterns", "performance audit", "check for code smells", "technical debt", or "code health check".
Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.