markdown-lint | Linter for markdown | Code Analyzer library

I'm editing a markdown file and see a few red squigglies in my document. I have flycheck working with markdown-lint, and ispell doing some other work to detect typos, repeated words, etc. But I can't immediately figure out why certain words are squiggled.

I've discovered that

• C-c ! n will take me to the next squiggly flycheck error
• C-, will take me to the next flyspell error
• M-$ will invoke ispell to help

So I've got everything working that's really needed. But it's a bit annoying that red squigglies represent different things, so I have to use different commands to get to things that look the same, and so it's impossible to tell which binding to use to jump to the next squiggly. And I'd like to know if there's a way, when point is on a squiggled thing, to know why it is squiggled. (I realize flycheck does a good job of showing reasons in minibuffer, but I don't think flyspell/ispell do).

I fear this is going to get worse as I try to add more tooling like WriteGood mode and possibly others.