zig fmt：格式化您的代码

Zig ships a built-in formatter so every project looks the same. The command zig fmt rewrites your code into the canonical Zig style.

Point zig fmt at a file and it reformats that file directly on disk, fixing indentation, spacing, and line breaks for you.

Give it a directory and zig fmt walks it recursively, tidying every .zig file it finds. One command formats an entire project.

There are no style options to argue about. Zig fmt has one fixed style, which ends formatting debates across every team and codebase.

The --check flag reports files that are not formatted and exits with an error, but it never edits anything. Perfect for verification.

Because --check returns a failing exit code, you can wire it into continuous integration to reject any unformatted code automatically.

Pass --stdin and zig fmt formats text piped in and prints the result out. Editors use this to format on save.

Most editors run zig fmt automatically when you save. Your code snaps into shape instantly, so you never think about layout again.

Remember the scope: zig fmt fixes layout only. It will not rename things or catch logic bugs; that is the compiler's job.

zig fmt mostly leaves your line breaks in literals and comments alone, so it cleans structure without erasing intentional layout.

Run the formatter before every commit. Clean, consistent diffs make reviews faster and keep the whole history readable for everyone.

In CI you want to fail the build when code is not formatted, without modifying any files. Which command works?

You met zig fmt: one canonical style, format files or folders, --check for CI, and editor-on-save to keep code clean effortlessly. 🧹