Asking for help in writing const and final linter rules

[ivangalkindeveloper]

I'm asking for help in writing two linter rules

1. It is necessary to analyze the addition of the keyword const in the declarations of a variable, if it is not final

• addTopLevelVariableDeclaration, addFieldDeclaration - is it possible to add the const keyword before the variable name
• addVariableDeclarationStatement - is it possible to add the keywords static and const before the name
  The question is how to parse the constant arguments of the initializer and whether the current initializer constructor is also const, since I have not yet found a way to do this

2. Adding the final keyword to a variable that never mutates
   The question is: is it possible to determine references to a variable and understand whether this variable is subject to mutation? If not, recommend adding the keyword final
   It seems to me that this rule is not implementable, since only the current file is analyzed, and I have not yet found ways in the package to determine the area where an current element may be present

I would be grateful for a code example with references to the necessary class properties to understand how these rules can be implemented