{div:class=navigation}
{table:width=100%}
{tr}
{td:width=33%}{align:left}[Previous|Find Usages] {span:class=sep}\| {span}{span:class=text}Find Usages{span}{align}{td}
{td:width=33%}{align:center}[Top|Quick Start] {span:class=sep}\| {span}{span:class=text}Quick Start{span}{align} {td}
{td:width=33%}{align:right}[Next|Code Style and Formatting] {span:class=sep}\| {span}{span:class=text}Code Style and Formatting{span}{align} {td}
{tr}
{table}
{div}

{redirect:https://www.jetbrains.com/idea/help/code-inspection.html|delay=0}

Inspections are built-in static code analysis tools that help you find probable bugs, locate dead code, detect performance issues and improve the overall code structure.

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

{span:class=shortcut}Analyze{span}
{span:class=shortcut}Inspect Code{span}
menu, or when you run certain inspection by its name via
{span:class=shortcut}Analyze{span}
{span:class=shortcut}Run Inspection by Name{span}
.

2. Navigate to the next/previous problem

The editor lets you quickly navigate between the highlighted problems via keyboard shortcuts. Press

{span:class=shortcut}F2{span}
to go to the next problem and Shift+F2 to go to the previous one. You can configure the severity of the problems through which the
{span:class=shortcut}F2{span}
key navigates in the
{span:class=shortcut}Settings{span}
{span:class=shortcut}Editor{span}
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

{span:class=shortcut}Analyze{span}
{span:class=shortcut}Inspect Code{span}
command.

4. Quick-fixes

Most inspections not only tell you where a problem is, but provide quick-fixes to deal with them right away. Just press

{span:class=shortcut}Alt{span}
+
{span:class=shortcut}Enter{span}
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

{span:class=shortcut}Shift{span}
+
{span:class=shortcut}Alt{span}
+
{span:class=shortcut}Ctrl{span}
+
{span:class=shortcut}I{span}
(
{span:class=shortcut}Shift{span}
+
{span:class=shortcut}Alt{span}
+
{span:class=shortcut}Cmd{span}
+
{span:class=shortcut}I{span}
for Mac) shortcut or use
{span:class=shortcut}Analyze{span}
{span:class=shortcut}Run Inspection by Name{span}
.

7. Highlighting level and power save mode

Another useful thing is the Hektor icon located on the status bar. It helps you switch highlighting levels: from none to syntax and inspections. At syntax level you don't get any warnings except when code can't be compiled.

The Hektor icon also lets you activate power save mode that helps conserve battery power by disabling highlighting and auto-popups.

8. Inspection profiles

And finally you can change the list of inspections enabled for a project by managing the inspection profiles via

{span:class=shortcut}Settings{span}
{span:class=shortcut}Inspections{span}
. If you want to share your inspection profile with your team, enable the Share profile checkbox, and check the inspections project files into VCS.

{div:class=navigation}
{table:width=100%}
{tr}
{td:width=33%}{align:left}[Previous|Find Usages] {span:class=sep}\| {span}{span:class=text}Find Usages{span}{align}{td}
{td:width=33%}{align:center}[Top|Quick Start] {span:class=sep}\| {span}{span:class=text}Quick Start{span}{align} {td}
{td:width=33%}{align:right}[Next|Code Style and Formatting] {span:class=sep}\| {span}{span:class=text}Code Style and Formatting{span}{align} {td}
{tr}
{table}
{div}