Jacob Garber:
The Coverity issue tracker has several IDE-like features, such as a usage finder and go-to definitions. This was adequate for most of my needs, and anything else I tracked down using vim and judicious use of grep. There are probably more efficient ways to do this (eg. ctags?), but this was sufficient for my purposes, since most Coverity problems only need a local understanding of the codebase. If you're looking to start tackling Coverity issues then #1405310, #1241824, #1241913, and #1241847 (and other issues of those types) look like a good place to get started. I'd be happy to help you through the workflow and review patches for simple fixes like these, but don't have the knowledge to do the more complex ones.
Sounds like I should be able to tackle at least the "local understanding" ones with my existing tools. Thank you for the pointers, will see what I can do.