domains / families / software-engineering / dx-code-analyzer-custom-rule-create

dx-code-analyzer-custom-rule-create

authentic

Create custom Code Analyzer rules for Regex (pattern matching), PMD (XPath/AST for Apex and metadata XML), and ESLint (LWC/JavaScript/TypeScript). Use when users want to enforce coding standards, ban patterns, detect hardcoded values, govern metadata, or add rules not in the built-in set. TRIGGER when: user says 'create a rule', 'ban System.debug', 'enforce naming convention', 'detect hardcoded IDs', 'custom rule', 'xpath rule', 'regex rule', 'add a PMD rule', 'enforce a policy', 'create a check for', 'flag this pattern', 'make a rule that catches', 'metadata rule', 'check permissions', 'enforce API version', 'eslint rule', 'lwc rule', 'override rule threshold', 'customize complexity', or describes a pattern to enforce. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), configure engines (use dx-code-analyzer-configure), or explain existing rules (use dx-code-analyzer-run).

When to use

• Creating new custom rules
• Enforcing team-specific coding standards
• Banning specific patterns
• Writing XPath expressions for PMD rules
• Writing regex patterns
• Setting up custom ESLint rules
• Enforcing metadata governance
• Overriding built-in rule thresholds

When not to use

• Running a scan against existing rules
• Configuring engines, prerequisites, CI/CD
• Explaining what an existing built-in rule means
• Writing Apex code or tests

Skill page

Source