ci: backronym ci to clean-install (#57)

Credit: @zkat
Reviewed-By: @jefflembeck

doc/cli/npm-ci.md

@@ -39,9 +39,10 @@ cache:
 
 This command is similar to `npm-install(1)`, except it's meant to be used in
 automated environments such as test platforms, continuous integration, and
-deployment. It can be significantly faster than a regular npm install by
-skipping certain user-oriented features. It is also more strict than a regular
-install, which can help catch errors or inconsistencies caused by the
+deployment -- or any situation where you want to make sure you're doing a clean
+install of your dependencies. It can be significantly faster than a regular npm
+install by skipping certain user-oriented features. It is also more strict than
+a regular install, which can help catch errors or inconsistencies caused by the
 incrementally-installed local environments of most npm users.
 
 In short, the main differences between using `npm install` and `npm ci` are:

lib/config/cmd-list.js

@@ -17,7 +17,9 @@ var shorthands = {
   't': 'test',
   'ddp': 'dedupe',
   'v': 'view',
-  'run': 'run-script'
+  'run': 'run-script',
+  'clean-install': 'ci',
+  'clean-install-test': 'cit'
 }
 
 var affordances = {
@@ -27,6 +29,8 @@ var affordances = {
   'ic': 'ci',
   'innit': 'init',
   'isntall': 'install',
+  'install-clean': 'ci',
+  'isntall-clean': 'ci',
   'dist-tags': 'dist-tag',
   'apihelp': 'help',
   'find-dupes': 'dedupe',
@@ -46,13 +50,13 @@ var affordances = {
   'rm': 'uninstall',
   'r': 'uninstall',
   'rum': 'run-script',
-  'sit': 'cit',
-  'urn': 'run-script'
+  'sit': 'cit'
 }
 
 // these are filenames in .
 var cmdList = [
   'ci',
+  'install-ci-test',
   'install',
   'install-test',
   'uninstall',