add-mlinter-rule

To add a custom rule to mlinter, you need to scaffold a new TRF module, register it in the TOML configuration, implement the Python static analysis logic, and generate corresponding tests and documentation stubs.

The TRF naming convention is a standardized identification format required by mlinter's discovery and validation workflows to properly detect, register, and apply custom static analysis rules across all models and configurations.

Avoiding duplicate mlinter rules requires running duplicate detection checks during the scaffolding workflow before assigning a new rule number and creating the TOML entry for your Python static analysis module.

Manual test and documentation scaffolding is not required for mlinter rule creation; the automated workflow generates test scaffolds and documentation stubs to ensure cross-model compatibility and proper integration.

Yes, mlinter custom rules apply across all models and configurations when you align the Python static analysis implementation with mlinter's TRF discovery workflow and properly wire the TOML entry.

A key limitation is that rule development strictly requires Python-based static analysis and adherence to the TRF naming convention; deviating from this discovery workflow will prevent mlinter from validating and integrating the custom rule.