Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
Use PIT (Pitest) mutation testing to identify weak tests and improve test quality in Java projects. Finds tests that pass but don't actually verify behavior correctly. Use when improving test suite quality beyo...
Performs security analysis on code changes including credential scanning, input validation, authentication checks, and dependency vulnerability assessment. Use when reviewing code for security issues or before...
Orchestrates quality checks at key lifecycle points: before edits, after edits, and before completion. Coordinates sub-skills (test-augmentation, doc-sync, coding-standards, security-review) to ensure consisten...
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 cover...
Validates and improves test coverage for code changes. Checks coverage thresholds, identifies untested code paths, and provides guidance on writing effective tests. Use after making code changes or when improvi...
Executes OpenAI Codex CLI for code analysis, refactoring, and automated editing. Activates when users mention codex commands, code review requests, or automated code transformations requiring advanced reasoning...
Scan for security vulnerabilities in dependencies, code patterns, and secrets. Uses project-documented tooling where available.
Perform automated code reviews with best practices.
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, highlight...
Improves IDE autocomplete and static analysis in Kirby projects with PHPDoc hints and Kirby IDE helper generation. Use when types are missing or IDE support is degraded.
Applies coding standards for clean, maintainable code. Use when: writing functions, handling errors, refactoring, or reviewing code style.
Detects code smells, anti-patterns, and debugging issues. Use when: fixing bugs, reviewing code quality, or refactoring.
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
Validates GitHub Copilot customization files (agents, skills, prompts, instructions) for correct format and structure. Use when checking if agent files are properly configured, troubleshooting agent issues, or...
Use when analyzing complex codebases for security vulnerabilities, performance issues, and structural patterns - provides systematic AST-based approach using ast-grep for comprehensive code understanding beyond...
Use when you need to check, verify, validate or understand code or structure of a file (often code related files or markdown) - automatically detects file type, finds appropriate LSP/linter in mise, and runs va...
Use when analyzing codebases for structure, finding symbols, tracing call paths, checking test coverage, or analyzing dependencies - provides instant AST-based code analysis using tree-sitter for Python, JavaSc...
Code Reviewer Specialist. Use this to review PRs, check security, and ensure code quality standards before merging.
建筑质量检查。验证代码语法、检查结构问题、确保细节完整。
Standard validation checklist to prove a security fix works and doesn’t regress behavior.
Repeatable process for an application security code review that produces prioritized findings and fix guidance.
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.
AI-powered code refactoring and modernization. Use this skill for code cleanup, technical debt reduction, framework migration, and improving code quality.
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...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.