pylint-checkers

Custom pylint checkers enforce domain-specific code quality rules by extending Pylint's checker classes. You define a checker class, register message types, and visit AST nodes to flag violations. This lets you catch project-specific patterns that built-in rules miss.

Built-in checkers cover standard Python code quality issues like naming conventions and unused variables. Custom checkers add rules specific to your codebase, architecture, or team standards, giving you fine-grained control over what violations to enforce.

Yes. Pylint checkers run as linting gates in CI/CD by invoking pylint from your build system, parsing output, and failing builds when violations exceed thresholds. Both built-in and custom checkers integrate seamlessly into automated workflows.

Package your checker as a Python module with entry points that Pylint discovers automatically. Register your checker class in a setup.py or pyproject.toml entry point, then users install your package and enable it in their pylint configuration.

Checker design requires planning the AST node types to visit, message templates, configuration options, and performance impact on large codebases. Robust error handling and clear documentation ensure the checker integrates smoothly across projects.