This could be done to review all checks, add additional text (and possibly remove unwanted items) before finally generating the final output.
Another variant would be something like some cli (or GUI) help to build the command line. f-r knows a lot of things which might be helpful: - The available mock configurations. - If there's a cache available. - Saved parameters from last run. - If there's an old review directory to handle.
With some user interaction, it might perhaps be somewhat easier to use f-r. OTOH, with the intended kind of users we have, this is perhaps not necessary.
Still other tasks could be to be helpful in the post-check stage, converting check results to issues, marking manual checks as passed/failed etc.
Login to comment on this ticket.