title: how to get arc lint to print what it is doing internally
body: <p>I have a project with arcanist setup along with phabricator for version control and code review management. There is a neat .arclint configuration setup currently using a mix of inbuilt linters (like filename) and external linters like cpplint, with setup for includes and excludes done.</p>
  <p>What is the best way to get this linter setup to a bitbucket-based tool doing the same thing? Essentially, <strong>is there a way to know how arc lint converts a .arclint file configuration to a command line argument</strong> with specifications of including files and severity warnings?</p>
  <p>I can use git to figure out a list of files changed, which is already part of arc lint, but I still want to understand what magic is arc lint running underneath to run the specific linter. And I know how bitbucket-pipelines work to run lint before every new merge.</p>
  <p>Here is a part of .arclint which I am trying to replicate</p>
  <pre><code>   &quot;linters&quot;: {
       &quot;chmod&quot;: {
         &quot;type&quot;: &quot;chmod&quot;
       },
       &quot;filename&quot;: {
         &quot;type&quot;: &quot;filename&quot;
       },
       &quot;merge-conflict&quot;: {
         &quot;type&quot;: &quot;merge-conflict&quot;
       },
       &quot;json&quot;: {
         &quot;type&quot;: &quot;json&quot;,
         &quot;include&quot;: [
           &quot;(^\\.arcconfig$)&quot;,
           &quot;(^\\.arclint$)&quot;,
           &quot;(\\.json$)&quot;
         ]
       },
       &quot;nolint&quot;: {
         &quot;type&quot;: &quot;nolint&quot;
       },
       &quot;xml&quot;: {
         &quot;type&quot;: &quot;xml&quot;,
         &quot;include&quot;: [
           &quot;(\\.xml$)&quot;
         ]
       },
       &quot;cpplinth&quot;: {
         &quot;type&quot;: &quot;cpplint&quot;,
         &quot;bin&quot; : [&quot;dev_tools/cpplint.py&quot;],
         &quot;include&quot;: [
           &quot;(\\.h$)&quot;,
           &quot;(\\.hpp$)&quot;
         ],
  
  </code></pre>