Total 30,580 skills, Code Quality has 1614 skills
Showing 12 of 1614 skills
L3 Worker. Analyzes single pattern implementation, calculates 4 scores (compliance, completeness, quality, implementation), identifies gaps and issues. Usually invoked by ln-640, can also analyze a specific pattern on user request.
Research standards/patterns via MCP Ref. Generates Standards Research for Story Technical Notes subsection. Reusable worker.
Configures ESLint, Prettier, Ruff, and .NET analyzers
Comprehensive quality gate integrating linting, type checking, specification review, and security auditing.
Meta-cognitive reasoning specialist for evidence-based analysis, hypothesis testing, and cognitive failure prevention. Use when conducting reviews, making assessments, debugging complex issues, or any task requiring rigorous analytical reasoning. Prevents premature conclusions, assumption-based errors, and pattern matching without verification.
Comprehensive code review checklist for pull requests
TypeScript strict patterns and best practices. When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
Analyze code complexity and find refactor targets using radon/gocyclo. Triggers: "complexity", "analyze complexity", "find complex code", "refactor targets", "cyclomatic complexity", "code metrics".
Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.
You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa
L3 Worker. Audits layer boundaries + cross-layer consistency: I/O violations, transaction boundaries (commit ownership), session ownership (DI vs local), async consistency (sync I/O in async), fire-and-forget tasks.
Coordinates linters, pre-commit hooks, and test infrastructure setup