sonarqube-integration
SonarQube integration via MCP for Java projects. The MCP server runs remotely and requires no local setup. Use natural language to query issues, analyze code, and check quality gates.
SonarQube integration via MCP for Java projects. The MCP server runs remotely and requires no local setup. Use natural language to query issues, analyze code, and check quality gates.
JaCoCo code coverage configuration for Java/Gradle projects. Covers report generation, coverage thresholds, multi-module aggregation, and SonarQube integration. Use when setting up or troubleshooting code coverage.
Semantic code analysis via LSP. Navigate code (definitions, references, implementations), search symbols, preview refactorings, and get file outlines. Use for exploring unfamiliar codebases or performing safe refactoring.
MCP (Model Context Protocol) server configurations for various IDEs including setup, troubleshooting, and discovery management
Expert on Move programming language - abilities (copy/drop/store/key), generics, phantom types, references, global storage operations, signer pattern, visibility modifiers, friend functions, inline optimization, and advanced type system. Triggers on keywords move language, abilities, generics, phantom type, borrow global, signer, friend, inline, type parameter
AI-assisted code review for bugs, style, performance, and security issues. Use this skill when reviewing code changes, pull requests, or when asked to check code quality.
i18n/l10n implementation for multi-language support. Use for translation setup, RTL support, and locale-aware formatting.
Use when the user wants to highlight code in markdown files, including inline code highlighting with {lang} prefix syntax, code blocks with language fences and titles, and transformer marks for diffs, highlights, focus, errors, and warnings. Always read this skill file when inserting code blocks or inline code in markdown.
This skill provides guidance for fixing LaTeX overfull hbox warnings by making synonym substitutions. It should be used when the task involves resolving LaTeX line-breaking issues by replacing words with synonyms from an allowed list, particularly when the goal is to reduce line width without changing meaning.
Expert guidelines for writing idiomatic, safe, and performant Rust code.
Guidance for creating polyglot source files that compile and run correctly as both Rust and C or C++. This skill applies when tasks require writing code that is valid in multiple languages simultaneously, exploiting comment syntax differences or preprocessor directives to create dual-language source files. Use this skill for polyglot programming challenges, CTF tasks, or educational exercises involving multi-language source compatibility.
Guides Test-Driven Development for this Neovim plugin project. Use when implementing new features or fixing bugs that require behavioral changes. Includes project-specific tooling (make test/lint/check) and Lua/Busted testing patterns. Follows strict RED-GREEN-REFACTOR cycle.
This skill should be used when the user asks to "open in nvim", "show in editor", "open file in nvim", "edit in nvim", "nvim open", "send to nvim", "open buffer", "view in neovim", or "open this in my editor". Requires NVIM_SOCKET environment variable to be set (automatic in worktree sessions). Not for editing files directly - this sends files to the user's nvim instance.
Invoke BEFORE writing PHP code. Provides coding standards and naming conventions.
Invoke before creating or modifying .neon files. Provides NEON syntax and Nette configuration conventions.
Codebase analysis tool for quality-first editing. Scan before edit to understand relationships, patterns, and impact.
Enforce code quality standards, test coverage, and static analysis. Use when working with code coverage thresholds, mutation testing, linting, code formatting, or quality gates. Maintains high code quality standards through automation.
Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback templates. Ensures consistent, constructive, and thorough code reviews across teams.
Biome 2.0+ linting and formatting for fast, unified code quality. Includes type inference, ESLint migration, CI integration, and 421 lint rules. Use when migrating from ESLint/Prettier or setting up new projects.
Activates when reviewing code, checking for security issues, or validating best practices. Use this skill for: security audits, performance reviews, React 19 pattern validation, TypeScript strict mode compliance, and OWASP vulnerability checks. Keywords: review, security, performance, audit, OWASP, vulnerability, best practice, lint
Use swiftfindrefs (IndexStoreDB) to list every Swift source file referencing a symbol. Mandatory for “find references”, “fix missing imports”, and cross-module refactors. Do not replace with grep/rg or IDE search.