Workflow for removing skip from newly passing tests

What should be the recommended workflow for removing `skip: true` from newline passing tests?

Let's say I have a huge test suite, with a few dozen `skip: true` tests, and I make a big refactor:

1. I run `pub run test --run-skipped` to see if any have failed. Oh, 37 failed.
2. But how many do I have skipped? Run `git grep "skip: true"`. 39 skipped!
3. Now how do I find the 2 that I fixed during the refactor?

I've been doing tricks with `pub run test |grep skip`, but this is still very icky when you have > 10 or so skipped tests.

Start by reproducing the reported workflow with `pub run test --run-skipped`, `git grep "skip: true"`, and the existing `pub run test | grep skip` workaround. Review the test runner's skipped-test output and determine whether a recommended workflow can be documented; done means a newcomer can identify newly passing skipped tests without manual comparison.

Written by the indexing model from the issue text.