create-tally-rule

Creating custom Dockerfile linting rules is automated by generating rule code, detection logic, unit tests, fixture data, and documentation together. This ensures new containerfile static analysis checks are fully implemented end-to-end.

To detect anti-patterns in BuildKit syntax, define detection logic that parses modern Dockerfile instructions. The rule implementation process ensures compatibility with BuildKit features while generating the necessary snapshots and unit tests to validate behavior.

A new Dockerfile static analysis check includes the rule code, detection logic, unit tests, fixture data, snapshots, and documentation. This end-to-end implementation ensures the linting rule is fully functional and tested within the project.

No, unit tests are generated automatically alongside the rule code and fixture data. The automation guides the entire workflow, ensuring the new linting rule has the necessary tests and snapshots created without manual boilerplate.

Yes, you can enforce container image best practices like caching by defining a custom rule. The automation handles creating the detection logic and tests needed to identify the anti-pattern and enforce the desired practice.