code-format

Code formatting standardizes styling rules across languages by coordinating tools like dotnet-format for C#/.NET and Prettier for JSON, YAML, Markdown, JavaScript, and TypeScript. Configuration files such as .editorconfig and .prettierrc.json define rules once, then apply them repository-wide to eliminate style violations and maintain consistency.

Yes, code formatting integrates with pre-commit hooks to automatically clean and validate code before commits. The Skill supports verify modes for non-destructive checking and respects project configuration files, enabling automated enforcement in CI pipelines and local development workflows.

The Skill applies dotnet-format to C# and .NET projects, and Prettier to JSON, YAML, Markdown, JavaScript, and TypeScript files. Both tools respect configuration files (.editorconfig, .prettierrc.json, .prettierignore) and support targeted file patterns for selective formatting.

Run the format-all.sh script included in the Skill to format your entire repository in one operation. For specific languages, use `dotnet format` for .NET projects or `npx prettier --write` for JSON, YAML, Markdown, and JavaScript/TypeScript files with your project's configuration rules applied.

Yes, the Skill respects .editorconfig, .prettierrc.json, and .prettierignore files in your project, ensuring formatting rules align with existing standards. This eliminates configuration duplication and enforces consistent conventions across your entire multi-language repository.

The Skill supports verify modes for non-destructive checking, allowing you to validate code against formatting rules before applying changes. This is useful for CI validation and pre-commit checks without modifying your codebase.