finally there is something:
checkstyle-IDEA since 4.24.0 features import of checkstyle config.
A solution is available now:
Please install CheckStyle-IDEA plugin (http://plugins.jetbrains.com/plugin/1065?pr=idea), it can be found via plug-in repository (Settings|Plugins|Browse repositories).
Go to Settings|Editor|Code Style|Java, choose a code style you want to import CheckStyle configuration to.
While still in the Editor > Code Style > Java setting, click on the 🛞 wheel icon, choose "Import Scheme > Checkstyle Configuration*",* and select a corresponding
checkstyle.xmlconfiguration file. Click OK.At the end you will see a message "CheckStyle configuration settings were imported to ... scheme".
If you encounter any problems, you can create a new issue for the CheckStyle plug-in here: https://github.com/jshiell/checkstyle-idea/issues. This issue is actually a duplicate of https://github.com/jshiell/checkstyle-idea/issues/126.
CheckStyle plug-in version where the feature is available is 4.24.0
Copied from https://youtrack.jetbrains.com/issue/IDEA-61520#comment=27-1292600
Answer from helt on Stack Overflowfinally there is something:
checkstyle-IDEA since 4.24.0 features import of checkstyle config.
A solution is available now:
Please install CheckStyle-IDEA plugin (http://plugins.jetbrains.com/plugin/1065?pr=idea), it can be found via plug-in repository (Settings|Plugins|Browse repositories).
Go to Settings|Editor|Code Style|Java, choose a code style you want to import CheckStyle configuration to.
While still in the Editor > Code Style > Java setting, click on the 🛞 wheel icon, choose "Import Scheme > Checkstyle Configuration*",* and select a corresponding
checkstyle.xmlconfiguration file. Click OK.At the end you will see a message "CheckStyle configuration settings were imported to ... scheme".
If you encounter any problems, you can create a new issue for the CheckStyle plug-in here: https://github.com/jshiell/checkstyle-idea/issues. This issue is actually a duplicate of https://github.com/jshiell/checkstyle-idea/issues/126.
CheckStyle plug-in version where the feature is available is 4.24.0
Copied from https://youtrack.jetbrains.com/issue/IDEA-61520#comment=27-1292600
UPDATE: supported since 4.24.0 plug-in version, see here for details.
Original answer from 2013:
Not possible yet, please star/vote to track the progress of the issue.
Plugin On GitHub
How to set it up


Codestyle and formatters
Checkstyle is the worst tool ever. Would you agree?
Add support for default IntelliJ IDEA formatting
Use IntelliJ code style in Checkstyle - Stack Overflow
Hi y'all,
My team would like to standardise code formatting and enforce it in CI. We've tried google-java-formatter but it doesn't look nearly as good as inteliJ's default settings.
Ideally, we'd like to export inteliJs defaults (to have the benefits of built in formatter) and use something that would enforce it on CI build. Has anyone done it? What are your pipelines like? Any tips and tricks?
I really do not understand the need for checkstyle. Imagine your build fails because you have an extra white space that you can't even see through naked eye. Java allows mulitple blank lines and as much white space as you want for a reason to have flexibility. I know it is possible for somoene to add accidently add 100s of blank new line but that is something no developer would ever do intentionally
Unfortunately it is not possible to do what you want for (at least) three reasons, the first two of which you have already raised:
While is possible to export a code style file from Intellij IDEA using File->Settings->Code Style->Java->{Click the Settings icon}->Select Export... from the popup menu, that exported XML file only contains the changes you have made from the default settings.
Those exported settings are in a format that is only meaningful to Intellij, so even if you could export every single Java code style setting to an XML file, you would then have to massively edit that file to make it meaningful to CheckStyle.
Finally, note that there is an open request for Intellij to do exactly what you want. See IDEA-149529:
Current export functionality for Code Styles is lacking. Only useful for other users of IntelliJ or as a backup. Only exports the diff between user defined settings and the built-in default. This makes it very difficult to produce a matching style for other formatting/beautification tools.
It would be helpful if the export had the option of exports ALL the settings IDEA uses.
However, there is an alternative approach. Instead of providing an Intellij IDEA file to Checkstyle, provide a Checkstyle file to Intellij IDEA...
Install the Checkstyle plugin, and then open two sets of one or more duplicated files in Intellij IDEA, one set configured to use IDEA's formatting and one set configured to Checkstyle's formatting.
Repeatedly tweak the Checkstyle settings until its opened file(s) are formatted to conform to the corresponding files formatted by IDEA. When the sets of files match create a Checkstyle XML rules file. Tedious, but only a one time activity.
Finally, you can then import your customized CheckStyle XML rules file into Intellij Idea, using Import Scheme -> CheckStyle Configuration as as shown in the screen shot below (if, and only if, you have installed the CheckStyle-IDEA plugin). This functionality did not exist when the OP was created. For more details see the following bug report: IDEA-61520 Codestyle from Checkstyle and in particular the response from JetBrains dated 2/8/16.
See also:
Intellij IDEA bug Configure code style from checkstyle #126
SO post IntelliJ IDEA code format from checkstyle configuration

I was looking for an answer to this too. I suppose you want to add it to your build process like I do. Since I saw no value in enforcing something that can't be automated, I settled on (haven't implemented yet) executing the style formatter as a pre-commit hook (I use git) https://www.jetbrains.com/help/idea/command-line-formatter.html against all files in the changelist. I use the defaults too, and this would be enough.
Since I don't have any customizations, I would not know if an exported code style xml would run the default in addition to the diff in the xml. Either way, there's no point in enforcing code style rules that can't be automated.