ameba-configuration

Ameba configuration enforces Crystal code style through a .ameba.yml file that defines lint, style, and performance rules with severity levels. Generate a default config with `ameba --gen-config`, then customize rule enablement, file globs, and exclusions to match your project's standards.

Ameba organizes rules into three categories: Lint rules catch code errors and potential bugs, Style rules enforce consistent formatting conventions, and Performance rules identify inefficient code patterns. Each category applies different severity levels to guide developers on issue priority.

Yes, Ameba's .ameba.yml supports both Globs to target code paths and Excluded to skip files and directories. You can also disable specific rules inline within your code and configure per-rule exclusions like ExcludeEmptyBlocks for fine-grained control.

Ameba supports inline rule disabling within Crystal source code, allowing you to suppress specific rules for particular code blocks. Configure per-rule options in .ameba.yml to set Enabled status and Severity levels, or disable rules temporarily where they conflict with your intent.

Ameba supports auto-correction across multiple Crystal codebases, allowing it to automatically fix detected style and performance issues. Run Ameba with auto-correct flags to apply fixes, then review and commit the changes to standardize code across your project.

Yes, Ameba's .ameba.yml configuration is portable and can be reused across multiple Crystal codebases. Share a base configuration across projects and customize Globs and rule severities per repository to enforce consistent standards while adapting to project-specific needs.