{
  "name": "cliff-jumper",
  "description": "A small CLI tool to create a semantic release and git-cliff powered Changelog",
  "options": [
    {
      "names": [
        "--help",
        "-h"
      ],
      "description": "Display help for command",
      "isPersistent": true,
      "priority": 10
    },
    {
      "names": [
        "--name",
        "-n"
      ],
      "description": "The package name to release",
      "isPersistent": true,
      "priority": 100,
      "args": [
        {
          "name": "name"
        }
      ]
    },
    {
      "names": [
        "--package-path",
        "-p"
      ],
      "description": "The path to the current package. For non-monorepos this is just \".\"",
      "isPersistent": true,
      "priority": 90,
      "args": [
        {
          "name": "path",
          "template": "folders"
        }
      ]
    },
    {
      "names": [
        "--dry-run"
      ],
      "description": "Whether the package should be bumped or not. When this is set no actions will be taken and only the release strategy will be logged"
    },
    {
      "names": [
        "--first-release"
      ],
      "description": "Whether this is the first release (skips bumping the version)'"
    },
    {
      "names": [
        "--mono-repo"
      ],
      "description": "Whether the package to be bumped resides in a mono repo,\nwhich enables Lerna-like scanning for what kind of version bump should be applied\nDefaults to \"true\" when \"org\" is set, false otherwise"
    },
    {
      "names": [
        "--no-mono-repo"
      ],
      "description": "Whether the package to be bumped resides in a mono repo,\nwhich enables Lerna-like scanning for what kind of version bump should be applied\nDefaults to \"true\" when \"org\" is set, false otherwise"
    },
    {
      "names": [
        "--org",
        "-o"
      ],
      "description": "The NPM org scope that should be used. This should be WITHOUT \"@\" sign or trailing \"/\"",
      "args": [
        {
          "name": "organisation"
        }
      ]
    },
    {
      "names": [
        "--preid"
      ],
      "description": "The \"prerelease identifier\" to use as a prefix for the \"prerelease\" part of a semver",
      "args": [
        {
          "name": "id"
        }
      ]
    },
    {
      "names": [
        "--commit-message-template",
        "-c"
      ],
      "description": "A custom commit message template to use.\nDefaults to \"chore({{name}}): release {{full-name}}@{{new-version}}\"\nYou can use \"{{new-version}}\" in your template which will be dynamically replaced with whatever the new version is that will be published.\nYou can use \"{{name}}\" in your template, this will be replaced with the name provided through \"-n\", \"--name\" or the same value set in your config file.\nYou can use \"{{full-name}}\" in your template, this will be replaced \"{{name}}\" (when \"org\" is not provided), or \"@{{org}}/{{name}}\" (when \"org\" is provided).",
      "args": [
        {
          "name": "template"
        }
      ]
    },
    {
      "names": [
        "--tag-template"
      ],
      "description": "A custom tag template to use.\nWhen \"org\" is provided this will default to \"@{{org}}/{{name}}@{{new-version}}\", for example \"@favware/cliff-jumper@1.0.0\"\nWhen \"org\" is not provided this will default to \"v{{new-version}}\", for example \"v1.0.0\"\nYou can use \"{{new-version}}\" in your template which will be dynamically replaced with whatever the new version is that will be published.\nYou can use \"{{org}}\" in your template, this will be replaced with the org provided through \"-o\", \"--org\" or the same value set in your config file.\nYou can use \"{{name}}\" in your template, this will be replaced with the name provided through \"-n\", \"--name\" or the same value set in your config file.\nYou can use \"{{full-name}}\" in your template, this will be replaced \"{{name}}\" (when \"org\" is not provided), or \"@{{org}}/{{name}}\" (when \"org\" is provided).",
      "args": [
        {
          "name": "template"
        }
      ]
    },
    {
      "names": [
        "--install",
        "-i"
      ],
      "description": "Whether to run npm install (or your package manager's equivalent) after bumping the version but before committing and creating a git tag. This is useful when you have a mono repo where bumping one package would then cause the lockfile to be out of date"
    },
    {
      "names": [
        "--skip-changelog"
      ],
      "description": "Whether to skip updating your CHANGELOG.md\ndefault \"true\" when CI=true, \"false\" otherwise"
    },
    {
      "names": [
        "--no-skip-changelog"
      ],
      "description": "Whether to skip updating your CHANGELOG.md\ndefault \"true\" when CI=true, \"false\" otherwise"
    },
    {
      "names": [
        "--skip-tag",
        "-t"
      ],
      "description": "Whether to skip creating a git tag\ndefault \"true\" when CI=true, \"false\" otherwise"
    },
    {
      "names": [
        "--no-skip-tag"
      ],
      "description": "Whether to skip creating a git tag\ndefault \"true\" when CI=true, \"false\" otherwise"
    },
    {
      "names": [
        "--verbose",
        "-v"
      ],
      "description": "Whether to print verbose information"
    },
    {
      "names": [
        "--version",
        "-V"
      ],
      "description": "Output the version number",
      "priority": 1
    }
  ]
}