1. On-the-fly code analysis
Most of the inspections run on-the-fly and display warnings or errors in the editor immediately as you type.
Inspections that are too complex to be run on on-the-fly are available when you perform code analysis for the entire project via Analyze → Inspect Code menu, or when you run certain inspection by its name via Analyze → Run Inspection by Name.
2. Navigate to the next/previous problem
Editor lets you quickly navigate between the highlighted problems via keyboard shortcuts. Press F2 to go to the next problem and Shift+F2 to the previous one. You can configure severity of problems through which the F2 key navigates in the Settings → Editor and tell it, for example, to always jump to the most serious issue in a file.
3. Run project-wide inspections
To get complete report with the inspection results for an entire project, use the Analyze → Inspect Code command.
Most inspections not only tell you where a problem is, but provide quick-fixes to deal with them right away. Just press Alt + Enter and choose a quick-fix.
5. Suppress warnings
When you don’t want warnings from this or that inspection for a specific statement or method, you can simply suppress them by pressing the right arrow on a quick-fix. Sometimes it may be a better solution than disabling the inspection for an entire project.
6. Run a single inspection
To run a single inspection by its name just press Shift + Alt + Ctrl + I (Shift + Alt + Cmd + I for Mac) shortcut or use Analyze → Run Inspection by Name.
7. Inspection profiles
You can always change the list of inspections enabled for a project by managing the inspection profiles via Settings → Inspections. If you want to share your inspection profile with your team, enable Share profile checkbox and submit inspections project files into VCS.