PR Summary

We have guidance for adding flags to commit messages to control which CI tasks run. Currently this starts with "If you know your changes do not need to be tested (this is very rare!)..." My instinct on reading this is to think this whole bullet point is not for me, and not bother reading the rest. So I re-ordered to start with the doc-only check, as I think that would be most commonly used, followed by skip circle. Also added some context for when it would be appropriate to use those.

PR Checklist

Documentation and Tests

• Has pytest style unit tests (and pytest passes)
• Documentation is sphinx and numpydoc compliant (the docs should build without error).
• New plotting related features are documented with examples.

Release Notes

• New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
• API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
• Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst