Total 50,522 skills, Code Quality has 2289 skills
Showing 12 of 2289 skills
Specifies the preferred syntax for asynchronous operations using async/await and onMount for component initialization. This results in cleaner and more readable asynchronous code.
Verify that a pull request or local changes fully implement the requirements described in a linked GitHub issue. Use when asked to "verify PR 123", "verify my changes", "check PR #123 coverage", "verify PR #123 against issue #42", "check local changes", or "do my changes cover issue 42". Analyzes the diff against issue requirements and reports either missing items or confirms 100% coverage.
Rust code style and conventions for Syncpack. Use when writing or modifying Rust code. Covers functional patterns, imports, naming, and quality standards.
This rule enforces the Don't Repeat Yourself principle to avoid code duplication and improve maintainability.
MoonBit (.mbt) coding standards and best practices. Use when writing, reviewing, or refactoring MoonBit code.
Deep code audit that finds dead wiring, silent failures, unfinished features, placeholder stubs, bloated files, and unnecessary complexity. Produces an actionable report with file:line references grouped by severity. Think of it as a senior dev doing a thorough PR review of the entire codebase. Triggers on: "code review", "audit the code", "review the code", "find dead code", "find placeholders", "check for stubs", "prune the code", "code cleanup", "implementation review", "completeness check", "find unused code".
Review and delivery persona for PR quality management and progress tracking in the SWE workflow.
TypeScript code style guide and formatting conventions. Use when writing TypeScript code, reviewing TypeScript files, refactoring .ts code, formatting TypeScript, or when working with TypeScript interfaces, classes, functions, or any .ts files. Apply these rules during code generation, code review, and when user mentions TypeScript style, formatting, conventions, semicolons, or code quality.
Expert in Gravito architecture and clean code. Trigger this for refactoring, design pattern implementation, or architectural audits.
Use when fixing Rubocop violations. Runs Rubocop to identify issues, applies fixes following project conventions, and explains non-obvious corrections.
Review code for quality, security, and pattern compliance, then auto-fix Critical/High issues. Grounds every finding in actual codebase reference files.
Acts as a Principal Software Engineer to review completed or in-progress work against project standards, tech stack choices, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.