I've found myself using a bunch of different tags relevant to what I'm doing while auditing contracts, I feel like having this new tag will be super useful for auditors to keep track of what severities/bugs they have already created a recommendation.
Sometimes I just tag some potential issues that I'm not entirely sure if they are indeed bugs or not, and other times I'm able to spot and validate that I find out an issue, in this occasion I go ahead and write down the recommendation to mitigate that issue.
My idea is by having this new tag, at the end of auditing the code base, the auditor can look up all these tags and start writing down the report, and then it can come back to the other vulnerabilities that have not been documented with its recommendation...
You can define and customize your tags (word and colour) as shown here. As an example, you can add the @audit-recommendation tag and map it to any colour you like (e.g. yellow).
You might need to reload the extension for it to work.
I've found myself using a bunch of different tags relevant to what I'm doing while auditing contracts, I feel like having this new tag will be super useful for auditors to keep track of what severities/bugs they have already created a recommendation.
Sometimes I just tag some potential issues that I'm not entirely sure if they are indeed bugs or not, and other times I'm able to spot and validate that I find out an issue, in this occasion I go ahead and write down the recommendation to mitigate that issue.
My idea is by having this new tag, at the end of auditing the code base, the auditor can look up all these tags and start writing down the report, and then it can come back to the other vulnerabilities that have not been documented with its recommendation...