fleetlint Policy for a fleet of repositories
v0.6
Getting started

format/configured

A formatter is configured

A capability: each stack checks it with its own tools. Implemented for cpp, dotnet, flutter, go, hugo, java, kotlin, node, php, python, ruby, rust.

Combine: all. Every implementation that runs must pass: each stack in the repository meets the requirement with its own tools.

Severitywarning
Tiers1, 2
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.3.1
Selected byfleetlint-recommended@v0.3.1

Requirement

Every stack has a formatter, configured in the repository or run by a hook, the task runner or CI, so formatting is never a review topic.

Why

Without one formatter every editor reformats differently and diffs fill with whitespace churn that hides the real change.

Fix

Add the stack’s formatter to the hooks and the fmt target (see https://fleetlint.org/stacks/).

Agent instruction: Add the stack’s formatter to the pre-commit hooks and the fmt target; reformat the code base in a separate commit.

See: https://fleetlint.org/baseline/#static-analysis


Generated by fleetlint docs from catalog v0.3.1.