GitHub
markdownlint-integration
Integrate markdownlint into development workflows including CLI usage, programmatic API, CI/CD pipelines, and editor integration.
☆ 75Voir le skill
Skills IA tools code quality
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
Catégories: tools code quality
tools code quality Effacer les filtres
Explorer
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.
☆ 75Voir le skill
GitHub
shfmt-formatting
Use when formatting shell scripts with shfmt. Covers consistent formatting patterns, shell dialect support, common issues, and editor integration.
☆ 75Voir le skill
GitHub
clippy-custom
Use when developing custom Clippy lints, implementing lint passes, and contributing to Clippy for Rust code standards.
☆ 75Voir le skill
GitHub
pylint-checkers
Use when pylint checkers including built-in checkers, custom checkers, and checker development.
☆ 75Voir le skill
GitHub
clippy-lints
Use when applying Clippy lint categories for Rust code including correctness, performance, style, and custom lint configuration.
☆ 75Voir le skill
GitHub
prettier-integration
Use when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.
☆ 75Voir le 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.
☆ 75Voir le skill
GitHub
checkstyle-custom
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
☆ 75Voir le skill
GitHub
eslint-custom
Use when custom ESLint rules and plugins including rule development, AST traversal, and publishing.
☆ 75Voir le skill
GitHub
credo-configuration
Use when configuring Credo static analysis for Elixir projects requiring customized code quality rules and settings.
☆ 75Voir le skill
GitHub
markdown-syntax-fundamentals
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
☆ 75Voir le skill
GitHub
prettier-plugins
Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
☆ 75Voir le skill
GitHub
checkstyle-rules
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
☆ 75Voir le skill
GitHub
rubocop-cops
Use when ruboCop cops including built-in cops, configuration, auto-correction, and development.
☆ 75Voir le skill
GitHub
biome-formatting
Use when formatting JavaScript/TypeScript code with Biome's fast formatter including patterns, options, and code style management.
☆ 75Voir le skill
GitHub
prettier-configuration
Use when prettier configuration including options, config files, ignore patterns, and formatting rules.
☆ 75Voir le skill
GitHub
pylint-configuration
Use when pylint configuration including pylintrc, message control, plugins, and scoring system.
☆ 75Voir le skill
GitHub
pylint-integration
Use when pylint CI integration including plugins, editor integration, and performance tuning.
☆ 75Voir le skill
GitHub
markdownlint-custom-rules
Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.
☆ 75Voir le skill
GitHub
checkstyle-configuration
Use when configuring Checkstyle for Java projects with XML config, custom checks, properties, and module setup.
☆ 75Voir le skill
GitHub
eslint-configuration
Use when eSLint configuration including config files, extends, plugins, and environment setup.
☆ 75Voir le skill
GitHub
code-quality-gate
Automated code quality checks before commits. Use before committing code, when finishing a feature, or when user mentions "ready to commit" or "quality check".
☆ 75Voir le skill
GitHub
strict-python-mode
Enforces type hints, docstrings, and Python best practices. Use when writing or refactoring Python code, creating new functions, or when user mentions "production-ready" or "type-safe" code.
☆ 75Voir le skill
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.