clean-code-refiner

You can enforce clean-code standards across a repository by generating a formal standards document through an interactive interview process, which captures conventions for naming, complexity, and testing to ensure consistent code quality.

Defining coding guidelines for single-responsibility and function size is best achieved through a structured interview-driven workflow that tailors conventions and outputs a formal standards document for your team's specific engineering needs.

To generate a clean-code standards document, you start an interactive interview that guides you through tailoring conventions, producing a formal markdown file at the path defined by your repository configuration or a default location.

Yes, you can apply specific clean-code changes on top of default coding standards by using overlay mode, which preserves embedded defaults while adding your customizations, or use override mode to replace defaults entirely.

The clean-code standards generator reads an optional configuration at .lattice/config.yaml to determine the output path, and automatically uses a default path if the configuration file is not present in your repository.

You should replace default engineering guidelines entirely using override mode when your team requires a completely bespoke standards document, rather than using overlay mode to simply apply changes on top of existing defaults.