GitHub
code-reviewer
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
☆ 75View skill
databases code quality AI Skills
Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
Categories: databases code quality
databases code quality Clear filters
Browse skills
GitHub
boy-scout-rule
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
☆ 75View skill
GitHub
credo-checks
Use when understanding and fixing common Credo check issues for Elixir code quality and consistency.
☆ 75View skill
GitHub
markdownlint-integration
Integrate markdownlint into development workflows including CLI usage, programmatic API, CI/CD pipelines, and editor integration.
☆ 75View skill
GitHub
ameba-configuration
Use when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
☆ 75View skill
GitHub
shfmt-formatting
Use when formatting shell scripts with shfmt. Covers consistent formatting patterns, shell dialect support, common issues, and editor integration.
☆ 75View skill
GitHub
clippy-custom
Use when developing custom Clippy lints, implementing lint passes, and contributing to Clippy for Rust code standards.
☆ 75View skill
GitHub
pylint-checkers
Use when pylint checkers including built-in checkers, custom checkers, and checker development.
☆ 75View skill
GitHub
clippy-lints
Use when applying Clippy lint categories for Rust code including correctness, performance, style, and custom lint configuration.
☆ 75View skill
GitHub
prettier-integration
Use when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.
☆ 75View skill
GitHub
ameba-custom-rules
Use when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.
☆ 75View skill
GitHub
checkstyle-custom
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
☆ 75View skill
GitHub
eslint-custom
Use when custom ESLint rules and plugins including rule development, AST traversal, and publishing.
☆ 75View skill
GitHub
credo-configuration
Use when configuring Credo static analysis for Elixir projects requiring customized code quality rules and settings.
☆ 75View skill
GitHub
markdown-syntax-fundamentals
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
☆ 75View skill
GitHub
prettier-plugins
Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
☆ 75View skill
GitHub
checkstyle-rules
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
☆ 75View skill
GitHub
rubocop-cops
Use when ruboCop cops including built-in cops, configuration, auto-correction, and development.
☆ 75View skill
GitHub
biome-formatting
Use when formatting JavaScript/TypeScript code with Biome's fast formatter including patterns, options, and code style management.
☆ 75View skill
GitHub
prettier-configuration
Use when prettier configuration including options, config files, ignore patterns, and formatting rules.
☆ 75View skill
GitHub
pylint-configuration
Use when pylint configuration including pylintrc, message control, plugins, and scoring system.
☆ 75View skill
GitHub
pylint-integration
Use when pylint CI integration including plugins, editor integration, and performance tuning.
☆ 75View skill
GitHub
markdownlint-custom-rules
Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.
☆ 75View skill
GitHub
checkstyle-configuration
Use when configuring Checkstyle for Java projects with XML config, custom checks, properties, and module setup.
☆ 75View skill
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.