add-code-inspector-rule

To create custom static analysis rules for Wolfram Language, you define a pattern and its handler in the CodeInspector Rules.wl file to detect risky constructs. This integrates custom checks into your automated reviews.

You add a lint rule to CodeInspector by updating Kernel/Tools/CodeInspector/Rules.wl with a new entry and its tests. This enables the linter to catch deprecated Wolfram Language patterns across your codebase.

You can automate code reviews by enforcing custom CodeInspector rules in CI. Adding a verification workflow alongside your rule entry in Rules.wl ensures automated static analysis catches style violations.

Integrating a new CodeInspector rule requires updating Kernel/Tools/CodeInspector/Rules.wl with the rule definition and adding corresponding tests. You must also add a verification workflow to complete the integration.

You should use custom static analysis rules for Wolfram Language code when teams need to standardize quality by enforcing coding standards. Custom rules capture and report patterns indicating risks or style violations across the codebase.