anchor.diff:          workdir: /app
   ```
   
  -And then the logic of the (simplified) [command hook][hooks] script in `hooks/command`:
  +The logic of the (simplified) [command hook][hooks] script in `hooks/command`:
   
   ```bash
   #!/bin/bash
  
positive.code: 
  The best place to get started is the [Buildkite Plugins] repository. You can also find third-party plugins with the `buildkite-agent` tag [on GitHub][third party plugins].
  
  We mostly write our plugins as shell scripts, so we've created a [plugin tester]
  docker image that simplifies writing BATS tests and getting your plugin tested (so meta).
  
  ### Anatomy of a plugin
  
  
negative.code: ## Plugin sources
  
  If you refer to a plugin just by name (say `detect-clowns`), it defaults to
  https://github.com/buildkite-plugins/detect-clowns-buildkite-plugin. If you used `myorg/detect-clowns` it would refer to https://github.com/myorg/detect-clowns-buildkite-plugin.
  
  You can also use a fully qualified git repository name like `https://github.com/buildkite-plugins/detect-clowns-buildkite-plugin.git` or `git@github.com:foo/bar.git#v1.3`, which
  lets you refer to your own private git repositories. Branches, tags and commits
  