Add README for the orb.

--combine-config   combine all given config files to be evaluated together

^this is going to be --combine in the next release.

Add the test command.

it's probably cool to validate if the orb is following the best practices

https://circleci.com/docs/2.0/orbs-best-practices/#orb-best-practices-guidelines

On https://circleci.com/orbs/registry/orb/kenfdev/conftest-orb#commands-install, the Orb Quickstart Guide shows

orbs:
  conftest-orb: kenfdev/[email protected]

While the Usage Examples show:

orbs:
  conftest: kenfdev/[email protected]

Note the different name contfest-orb vs conftest. The later is cleaner I think.

Reference:

https://github.com/CircleCI-Public/circleci-cli-orb/blob/master/src/commands/install.yml

First up, thanks for writing this. I just used it successfully to install Conftest in one of my runs.

I think the step names could be improved

Note that "Download the CLI" out of context of the task doesn't tell the user which CLI is being installed. The names need to carry all of the context with them. I'd suggest instead "Installing Conftest"

Note:

• Install rather than download, simply because that's the name of the command
• Installing rather than install as the standard CircleCI output is written in present progressive