add-pr-comment | uses: mshick/add-pr-comment@v2 | Continous Integration library

To achieve what you want, you would have to use a sceipt or a shell command (which I don't know as it depends on the context) to extract just the part of the command output you want (e.g: Your code has been rated at 3.31/10), then add it as env variable (or output) to use it in the next step.

I would do something like this in your job:

You can create a step that gets the coverage to an output variable that then can be accessed by the next step.

Notice that for utilizing this method you will need to give the step and id and the set output variable a variable name so that you can access it in follow up steps within the same job.

Sample with your workflow below, but if you want to see a running demo here is the repo https://github.com/meroware/demo-coverage-set-output