Total 43,892 skills, Code Quality has 2055 skills
Showing 12 of 2055 skills
Execute iterative refinement workflows with validation loops until quality criteria are met. Use for test-fix cycles, code quality improvement, performance optimization, or any task requiring repeated action-validate-improve cycles.
Checklists and anti-patterns for reviewing Go code. Covers API design, error handling, concurrency, interfaces, safety, performance, naming, testing, functional options, logging, and deterministic simulation testing.
Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests.
Run Rust benchmarks and compare performance with the C implementation
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.
Request interactive code review from users using the agent-review CLI tool. Automatically captures user feedback on code changes.
Readable primary-flow–first code structuring with minimal boundaries, atomic composition, and contract-driven unit tests
Learn the rules of packlets for managing a JavaScript/TypeScript project. Use this skill whenever a user mentions packlets or when working in a project with packlets (src/packlets) directory.
This skill should be used when the user asks to "review code", "code review", "check my code", "audit code", "find bugs", "security review", "performance review", or any ServiceNow code quality assessment.
Session opener. Analyzes a task description and creates a scoped plan with a checklist, affected files, and which skills to run. Use at the start of every coding session before writing any code.
Automatically analyze performance issues when user mentions slow pages, performance problems, or optimization needs. Performs focused performance checks on specific code, queries, or components. Invoke when user says "this is slow", "performance issue", "optimize", or asks about speed.
Validates code changes against DeepRead's mandatory patterns and standards defined in AGENTS.md. Use this after writing or modifying code to catch violations before committing.