Total 54,018 skills, Code Quality has 2434 skills
Showing 12 of 2434 skills
Apply the Tell Don't Ask (TDA) principle when reviewing, writing, or refactoring object-oriented code. Use this skill whenever the user asks about OOP design, mentions getters/setters, wants to review a class for encapsulation issues, asks how to move logic closer to data, or asks why code feels "procedural" despite using classes. Also trigger when the user asks to refactor code that queries an object's state before making decisions externally. This skill should kick in for any code review or design question involving data access patterns, encapsulation, or how objects should collaborate.
Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
This skill should be used when setting up code quality tooling with ESLint v9 flat config, Prettier formatting, Husky git hooks, lint-staged pre-commit checks, and GitHub Actions CI lint workflow. Apply when initializing linting, adding code formatting, configuring pre-commit hooks, setting up quality gates, or establishing lint CI checks for Next.js or React projects.
Apply the "How I Made Your Machine" coding style guide to implementation, refactoring, and code review tasks across TypeScript, Rust, and Python. Use when a request asks for this style guide, when improving maintainability and type safety, when modeling domain concepts with explicit variants/types, or when enforcing behavior-first testing.
Elevate a working PR: hindsight review, refactor, simplify, test audit, docs, quality gates. Composes: hindsight-reviewer agent, /refactor, /simplify, /update-docs, /check-quality, /distill. Use when: PR works but could be better. "How would we do this knowing what we know now?"
Diagnose and fix errors with Codex delegation. Traces error to root cause, researches approach, delegates fix, verifies. Use when: bug reports, error messages, stack traces, test failures.
Evaluate and improve code modularization using the Balanced Coupling Model. Analyzes coupling strength, connascence types, and distance to identify refactoring opportunities and architectural improvements. Use when reviewing code architecture, refactoring modules, or designing new systems.
Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. For ambiguous, high-risk, or broad-scope issues, stop and route to write-plan first.
Route-aware gap analysis. For Brownfield - uses /speckit.analyze to compare specs against implementation. For Greenfield - validates spec completeness and asks about target tech stack for new implementation. This is Step 4 of 6 in the reverse engineering process.
TypeScript and JavaScript development standards for modern web and Node.js development. Covers strict TypeScript configuration, type safety patterns, ESM modules, async/await, testing with Jest/Vitest, and security best practices. Use when working with .ts, .tsx, .js, .mjs files, package.json, tsconfig.json, or when asking about TypeScript/JavaScript best practices.
Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.
Clean Code, Dart Guidelines & Documentation