Total 30,711 skills, Code Quality has 1621 skills
Showing 12 of 1621 skills
Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality
Have Codex CLI review uncommitted code changes. Claude Code then fixes valid issues and rebuts invalid ones. Codex re-reviews. Repeat until consensus. Codex never touches code — it only reviews.
Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Use when wanting to understand your coding patterns over time.
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
Iterative refinement workflow for polishing code, documentation, or designs through systematic evaluation and improvement cycles. Use when refining drafts into production-grade quality.
TypeScript, React, and Node.js coding standards: naming, types, hooks, components, error handling, refactoring, code review. Use when creating/editing TS/JS/React files, naming variables or components, designing API endpoints, handling async, structuring components, or when the user asks "how should I name...", "what's the best way to...", "is this good practice...", "can you review this code". Keywords: TypeScript, React, hooks, React Query, Jest, RTL, naming, immutability. Do not load for: CSS-only changes, documentation writing, JSON config edits, shell scripts.
Remove AI-style code slop from a branch by reviewing diffs, deleting inconsistent defensive noise, and preserving behavior and local style.
This skill should be used when implementing code that requires SOLID principles and clean code practices. It provides detailed guidance on Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles with comparison examples in TypeScript.
WPILib and FRC robot programming best practices, design patterns, and code guidance for Java. Use when writing, reviewing, or explaining WPILib robot code—command-based project structure, subsystems, autonomous routines, RobotContainer layout, command definition patterns (inline, factory, subclass), or Constants organization.
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.
Guides strict Test-Driven Development (TDD) using the Red-Green-Refactor cycle. Ensures no production code is written without a prior failing test. Use this skill when implementing new features, fixing bugs, or refactoring code to ensure high test coverage and design quality. Triggers on phrases like 'TDD', 'write tests first', 'test-driven', 'red-green-refactor', 'watch it fail', 'test first', or 'behavior driven'.
Use this to verify whether the work meets requirements when completing tasks, implementing main features, or before merging.