rubocop-cops
Use when ruboCop cops including built-in cops, configuration, auto-correction, and development.
Use when ruboCop cops including built-in cops, configuration, auto-correction, and development.
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
Swift code style conventions for clean, readable code. Use when writing Swift code to ensure consistent formatting, naming, organization, and idiomatic patterns.
Use when prettier configuration including options, config files, ignore patterns, and formatting rules.
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
Use when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
Use when configuring Clippy for Rust projects with TOML config, lint groups, attributes, and workspace setup.
Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.
Use when configuring Dialyzer for Erlang/Elixir type checking and static analysis.
Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
Use when eSLint configuration including config files, extends, plugins, and environment setup.
This skill should be used when working with C++ projects, CMakeLists.txt, Ninja, clang-tidy, clang-format, GoogleTest, Catch2, or Modern C++ (C++11-23) language patterns. Provides comprehensive C++ ecosystem patterns and best practices.
Use when pylint checkers including built-in checkers, custom checkers, and checker development.
Use when formatting shell scripts with shfmt. Covers consistent formatting patterns, shell dialect support, common issues, and editor integration.
Use when applying Clippy lint categories for Rust code including correctness, performance, style, and custom lint configuration.
Use when configuring shfmt for shell script formatting including .shfmt.toml setup, EditorConfig integration, and project-specific settings.
Use when configuring Checkstyle for Java projects with XML config, custom checks, properties, and module setup.
Use when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
Use when configuring Credo static analysis for Elixir projects requiring customized code quality rules and settings.
Use when applying Biome's linting capabilities, rule categories, and code quality enforcement to JavaScript/TypeScript projects.
Use when understanding and fixing common Credo check issues for Elixir code quality and consistency.
Use when developing custom Clippy lints, implementing lint passes, and contributing to Clippy for Rust code standards.
Performs code quality checks and reviews for ComposeWebView. Validates expect/actual implementations, KDoc coverage, Spotless formatting, and multiplatform patterns. Use when reviewing PRs, checking code quality, or validating new features.