Total 30,695 skills, Code Quality has 1620 skills
Showing 12 of 1620 skills
Orchestrates Gang of Four design pattern implementations across 8 languages. Analyzes user problems to select optimal pattern(s) from creational, structural, and behavioral categories. Provides concrete, production-ready implementations with explanations and trade-offs.
Quick reference for n8n patterns. Full docs /AGENTS.md
This skill guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use it when users request to eliminate code duplication, refactor repetitive code, apply the DRY principle, or mention code smells like copy-paste code, magic numbers, or repeated logic. It implements a 4-step workflow from identifying repetition to verified refactoring.
Run a comprehensive pull request review using multiple specialized agents. Each agent focuses on a different aspect of code quality, such as comments, tests, error handling, type design, and general code review. The skill aggregates results and provides a clear action plan for improvements. Triggers include "review PR", "analyze pull request", "code review", and "PR quality check".
Review one change set in one mode (`pr` or `local`) for correctness, security, tests, and scope, and return a clear go/no-go decision. Triggers: review pr, review local, readiness check, pre-merge review.
Eamon Hyland's opinionated tooling and conventions for TypeScript projects. Use when setting up new projects, configuring a linter, monorepos, library publishing, or when the user mentions Eamon's preferences.
Analyze code for performance and efficiency improvements
Analyze Go function lengths within a workspace and generate statistics (p50, p90, p99). Use when you need to audit function complexity, identify long functions, or generate code metrics for Go projects. Only analyzes files matching **/*.go within the current workspace, excluding dependencies.
Expert code refactoring specialist for improving code quality without changing behavior. Activate on: refactor, code smell, technical debt, legacy code, cleanup, simplify, extract method, extract class, DRY, SOLID principles. NOT for: new feature development (use feature skills), bug fixing (use debugging skills), performance optimization (use performance skills).
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Detect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.
Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.