Total 30,488 skills, Code Quality has 1608 skills
Showing 12 of 1608 skills
This skill should be used when making design decisions, evaluating trade-offs, assessing code quality, or when "engineering judgment" or "code quality" are mentioned.
Remove AI-generated code slop from the current branch. Use when the user says "deslop" or asks to clean up AI slop, remove AI code patterns, or clean the branch before committing.
Check which Rust lines are not covered by Rust tests.
Maps codebase structure, queries symbols, traces call paths, and analyzes dependencies. Use when exploring unfamiliar code, finding function callers/callees, detecting circular imports, or generating project overviews.
Use when applying Biome's linting capabilities, rule categories, and code quality enforcement to JavaScript/TypeScript projects.
Validate TypeScript/JavaScript code quality with ESLint, Prettier, type checking, and security analysis. Use for TypeScript/JS codebases to ensure code quality and standards.
Verifies code changes by running tests and generation scripts
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.
Automated code review with security, performance, and best practices analysis. Use when reviewing pull requests or analyzing code for vulnerabilities, performance issues, or maintainability concerns.
ALWAYS use before attempting any fix. Never jump to solutions - investigate root cause first. Use when encountering any technical issue, bug, test failure, or unexpected behavior.
Request interactive code review from users using the agent-review CLI tool. Automatically captures user feedback on code changes.
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.