Prettier format fixes

[atomist:generated]
[atomist-skill:atomist/prettier-skill]

.eslintrc.json

@@ -19,14 +19,10 @@
     "project": "tsconfig.json",
     "sourceType": "module"
   },
-  "plugins": [
-    "@typescript-eslint"
-  ],
+  "plugins": ["@typescript-eslint"],
   "rules": {
     "@typescript-eslint/no-explicit-any": "off",
-    "@typescript-eslint/no-floating-promises": [
-      "error"
-    ],
+    "@typescript-eslint/no-floating-promises": ["error"],
     "prettier/prettier": [
       "error",
       {

CODE_OF_CONDUCT.md

@@ -10,23 +10,23 @@ race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive
 environment include:
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+-   Using welcoming and inclusive language
+-   Being respectful of differing viewpoints and experiences
+-   Gracefully accepting constructive criticism
+-   Focusing on what is best for the community
+-   Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-- The use of sexualized language or imagery and unwelcome sexual
-  attention or advances
-- Trolling, insulting/derogatory comments, and personal or political
-  attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or
-  electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate
-  in a professional setting
+-   The use of sexualized language or imagery and unwelcome sexual
+    attention or advances
+-   Trolling, insulting/derogatory comments, and personal or political
+    attacks
+-   Public or private harassment
+-   Publishing others' private information, such as a physical or
+    electronic address, without explicit permission
+-   Other conduct which could reasonably be considered inappropriate
+    in a professional setting
 
 Project maintainers are responsible for clarifying the standards of
 acceptable behavior and are expected to take appropriate and fair

CONTRIBUTING.md

@@ -25,21 +25,21 @@ If you do not find an open issue related to your contribution and
 discussions in the Slack community are positive, the next thing to do
 is to create an issue in the appropriate GitHub repository.
 
-- Before we can accept any code changes into the Atomist codebase,
-  we need to get some of the legal stuff covered. This is pretty
-  standard for open-source projects. We are using
-  [cla-assisant.io][cla-assistant] to track our Contributor License
-  Agreement (CLA) signatures. If you have not signed a CLA for the
-  repository to which you are contributing, you will be prompted to
-  when you create a pull request (PR).
-- Be sure there is an open issue related to the contribution.
-- Code contributions should successfully build and pass tests.
-- Commit messages should follow the [standard format][commit] and
-  should include a [reference][ref] to the open issue they are
-  addressing.
-- All code contributions should be submitted via
-  a [pull request (PR) from a forked GitHub repository][pr].
-- Your PR will be reviewed by an Atomist developer.
+-   Before we can accept any code changes into the Atomist codebase,
+    we need to get some of the legal stuff covered. This is pretty
+    standard for open-source projects. We are using
+    [cla-assisant.io][cla-assistant] to track our Contributor License
+    Agreement (CLA) signatures. If you have not signed a CLA for the
+    repository to which you are contributing, you will be prompted to
+    when you create a pull request (PR).
+-   Be sure there is an open issue related to the contribution.
+-   Code contributions should successfully build and pass tests.
+-   Commit messages should follow the [standard format][commit] and
+    should include a [reference][ref] to the open issue they are
+    addressing.
+-   All code contributions should be submitted via
+    a [pull request (PR) from a forked GitHub repository][pr].
+-   Your PR will be reviewed by an Atomist developer.
 
 [cla-assistant]: https://cla-assistant.io/
 [commit]: http://chris.beams.io/posts/git-commit/
@@ -52,14 +52,14 @@ Please go through the checklist below before reporting a
 problem. There's a chance it may have already been reported, or
 resolved.
 
-- Check if you can reproduce the problem in the latest version of
-  the project.
-- Search the [atomist-community Slack][slack] community for common
-  questions and problems.
-- Understand which repo the bug should be reported in.
-- Scan the list of issues to see if the problem has previously been
-  reported. If so, you may add a comment to the existing issue
-  rather than creating a new one.
+-   Check if you can reproduce the problem in the latest version of
+    the project.
+-   Search the [atomist-community Slack][slack] community for common
+    questions and problems.
+-   Understand which repo the bug should be reported in.
+-   Scan the list of issues to see if the problem has previously been
+    reported. If so, you may add a comment to the existing issue
+    rather than creating a new one.
 
 You went through the list above and it is still something you would
 like to report? Then, please provide us with as much of the context,
@@ -74,11 +74,11 @@ the bug report template below if you like.
 
 At a minimum include the following:
 
-- Where did you find the bug? For example, did you encounter the bug
-  in chat, the CLI, somewhere else?
-- What version are you using?
-- What command were you using when it happened? (including
-  parameters where applicable)
+-   Where did you find the bug? For example, did you encounter the bug
+    in chat, the CLI, somewhere else?
+-   What version are you using?
+-   What command were you using when it happened? (including
+    parameters where applicable)
 
 ```
 [Description of the problem]

README.md

@@ -16,8 +16,8 @@ Atomist Skill to run NPM scripts
 
 Connect and configure this integration:
 
-- **GitHub**
-- **Slack**
+-   **GitHub**
+-   **Slack**
 
 The **GitHub** integration must be configured in order to use this skill. At least one repository must be selected.
 We recommand that you configure the **Slack** integration.

SECURITY.md

@@ -3,8 +3,8 @@
 This document outlines security procedures and general policies for the
 Atomist Open Source projects as found on https://github.com/atomist.
 
-- [Reporting a Vulnerability](#reporting-a-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
+-   [Reporting a Vulnerability](#reporting-a-vulnerability)
+-   [Disclosure Policy](#disclosure-policy)
 
 ## Reporting a Vulnerability
 
@@ -32,7 +32,7 @@ When the security team receives a security bug report, they will assign it
 to a primary handler. This person will coordinate the fix and release
 process, involving the following steps:
 
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes
-  will be released as fast as possible to NPM.
+-   Confirm the problem and determine the affected versions.
+-   Audit code to find any potential similar problems.
+-   Prepare fixes for all releases still under maintenance. These fixes
+    will be released as fast as possible to NPM.

tsconfig.json

@@ -8,9 +8,7 @@
     "declaration": true,
     "declarationMap": true,
     "sourceMap": true,
-    "lib": [
-      "DOM"
-    ],
+    "lib": ["DOM"],
     "strict": false,
     "forceConsistentCasingInFileNames": true,
     "noImplicitReturns": true,
@@ -25,9 +23,7 @@
     "lib/**/*.ts",
     "test/**/*.ts"
   ],
-  "exclude": [
-    ".#*"
-  ],
+  "exclude": [".#*"],
   "compileOnSave": true,
   "buildOnSave": false,
   "atom": {