lint-and-fix

Automatically format code and fix lint violations by running trunk-based tooling via make format and make lint commands. The skill iteratively applies minimal fixes and re-checks until both formatting and lint checks pass for a compliant codebase.

The best way to resolve linter violations across multiple modules is using an automated lint-and-fix process. It runs trunk check via make lint, applies minimal fixes to violations, and progressively verifies until all checks pass.

Yes, this automated lint and format workflow works with trunk-based development. It relies on trunk fmt and trunk check commands executed through make targets to standardize style and resolve violations across the codebase.

Standardize code style and ensure lint checks pass before merging by using an automated formatting and lint pipeline. It runs trunk fmt for style standardization and trunk check for violation detection, iterating until both pass.

Code may still have lint violations after running the formatter because formatting only fixes style issues. You need to run make lint to detect violations and apply minimal fixes, then progressively re-check until both format and lint pass for a clean state.