Skip to main content

Rules

Rules define the checks that guide a Maintain run. Each rule captures a focused quality standard, pattern, or constraint that Artemis can evaluate consistently across your codebase.

Every rule in Artemis includes the following attributes:

  • Rule Name A descriptive title (e.g., Error and Exception Handling, Input Validation).

  • Description Explains the purpose of the rule, what it enforces, and why it matters. Example: Ensures all user inputs are validated and sanitized to prevent vulnerabilities and maintain data integrity.

  • Importance Level Defines how critical the rule is for your project:

    • Mandatory -> Must always be followed.
    • Essential -> Strongly recommended for correctness and stability.
    • Preferred -> Encouraged for maintainability and best practices.
    • Advisory -> Optional recommendation.

  • Enabled / Disabled You can toggle each rule on or off based on project needs.

Creating a rule​

Step 1: Open the rule panel​

Navigate to Maintain > Rules.

Step 2: Choose or add a rule​

rule 1

Use the model prompt to describe the rule you want Artemis to create, or select one of the built-in rule templates below the chat bar. You can also continue from the sidebar by selecting an existing rule and following the same flow.

rule 2

Step 3: Review the generated rule​

Artemis opens a rule draft based on the model output or the selected built-in template. Review the proposed rule before moving forward.

rule 3

Step 4: Apply the rule and continue​

Artemis opens a rule draft, may ask clarifying questions you can answer, and then you can apply the rule to proceed. rule draft with apply action

Step 5: Review the resulting status​

If the rule produces no findings, it is marked as Don't. If Artemis finds issues, they appear as Do items that you can continue working through in the maintenance flow. rule 5

Rule outcome behavior​

Rules are evaluated as part of the Maintain workflow, and the result determines how the rule is surfaced:

  • Don't indicates that the rule did not identify actionable issues.
  • Do indicates that the rule found issues and can continue into the remediation flow.
  • Apply lets the user approve the generated rule so the workflow can advance to the next stage.

By defining rules, you can:​

  • Enforce consistent coding standards across teams
  • Detect risky or non-compliant patterns early
  • Provide actionable feedback to developers
  • Improve reliability, security, and maintainability

Next step​

Proceed to review and resolve issues.

Last updated on by Rozhin Khalilian