1. It'd save a lot of time if one could just click a Markdown PR description and start editing it, without entering edit mode first.
2. Thanks to the following prompt, I barely write PR descriptions these days.
> Run `gh pr view` then `gh pr edit` to fill out the PR description. Use my words verbatim as much as possible. Be brief. Use tasteful markdown formatting.
Sure - imagine my PR adds one new test which test one new function.
Starting from the test, allow me to step through the program execution, just like a debugger, to observe variables, surrounding code, and the complete file.
If you read only the covered lines of code in a linear way, you'd miss the refactoring opportunities because you aren't looking at the rest of the file.
Very glad you're working on this! Here is my wish list as a code reviewer:
1. Allow me to step through the code execution paths that have been modified in the pull request, based on the tests that have been modified.
2. Allow me to see the data being handled in variables as I look through the code.
3. Allow me to see code coverage of each part of the code.
4. Show me the full file as I am navigating through the program execution so that I can feel the level of abstraction and notice nearby repetition or code that would benefit from being cleaned up.
Check out the papers on Inspiratory Muscle Training (IMT) and bridge swallowing.