docs: Cleanup according to recommended style

Author: epage

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,3 @@
+assert_cli version
+rust version
+OS and version

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,4 @@
+- [ ] Tests created for any new feature or regression tests for bugfixes.
+- [ ] `cargo test` succeeds
+- [ ] `cargo +nightly clippy` succeeds
+- [ ] `cargo +nightly fmt -- --write-mode=diff` succeeds

CONTRIBUTING.md

@@ -2,33 +2,21 @@ Thanks for wanting to contribute!
 
 Feel free to create issues or make pull requests, we'll try to quickly review them.
 
-If you need to reach out to us, find a relevant [issue](https://github.com/killercup/assert_cli/issues) or open a new one.
-
-# Issues
-
-Some helpful pieces of information when reporting issues
-* assert_cli version
-* rust version
-* OS and version
+If you need to reach out to us, find a relevant [issue][Issues] or open a new one.
 
 # Pull Requests
 
 ## Project Ideas
 
-If you're looking for things to do check out the [open issues](https://github.com/killercup`/assert_cli/issues).
-Or take a grep through [all TODO comments](https://github.com/killercup/assert_cli/search?q=TODO) in the code and feel free to help us out there!
+If you're looking for things to do check out the [open issues][Issues].
+Or take a grep through [all TODO comments][TODO] in the code and feel free to help us out there!
 
 ## Best Practices
 
-We appreciate your help as-is.  We'd love to help you through the process for contributing.  We have some suggestions to help make things go more smoothly.
+We appreciate your help as-is. We'd love to help you through the process for contributing. We have some suggestions to help make things go more smoothly.
 
 Before spending too much time on a PR, consider opening an issue so we can make sure we're aligned on how the problem should be solved.
 
-🌈 **Here's a checklist for the perfect pull request:**
-- [ ] Make sure existing tests still work by running `cargo test` locally.
-- [ ] Add new tests for any new feature or regression tests for bugfixes.
-- [ ] Install [Clippy](https://github.com/Manishearth/rust-clippy) and run `rustup run nightly cargo clippy` to catch common mistakes (will be checked by Travis)
-
 # Releasing
 
 When we're ready to release, a project owner should do the following
@@ -39,3 +27,6 @@ When we're ready to release, a project owner should do the following
 - Create a github release
   - Identify what fixes, features, and breaking changes are in the release.
 - Run `cargo publish` (run `cargo login` first if needed)
+
+[Issues]: https://github.com/killercup/assert_cli/issues
+[TODO]: https://github.com/killercup/assert_cli/search?q=TODO

Cargo.toml

@@ -9,7 +9,7 @@ homepage = "https://github.com/killercup/assert_cli"
 documentation = "http://docs.rs/assert_cli/"
 readme = "README.md"
 categories = ["development-tools::testing"]
-keywords = ["cli", "testing", "assert", "command", "line"]
+keywords = ["cli", "testing", "assert", "command-line-interface"]
 build = "build.rs"
 
 [[bin]]

README.md

@@ -2,11 +2,14 @@
 
 > **Test CLI Applications** - This crate checks the output of a child process is as expected.
 
-[![Build Status](https://travis-ci.org/killercup/assert_cli.svg)](https://travis-ci.org/killercup/assert_cli) [![Documentation](https://img.shields.io/badge/docs-master-blue.svg)][Documentation] ![License](https://img.shields.io/crates/l/assert_cli.svg) [![crates.io](https://img.shields.io/crates/v/assert_cli.svg)](https://crates.io/crates/assert_cli)
+[![Build Status](https://travis-ci.org/killercup/assert_cli.svg)][Travis]
+[![Documentation](https://img.shields.io/badge/docs-master-blue.svg)][Documentation]
+![License](https://img.shields.io/crates/l/assert_cli.svg)
+[![crates.io](https://img.shields.io/crates/v/assert_cli.svg)][Crates.io]
 
 ## Install
 
-For your tests, just add it to your `Cargo.toml`:
+For your tests, add it to your `Cargo.toml`:
 
 ```toml
 [dev-dependencies]
@@ -71,9 +74,9 @@ More detailed information is available in the [documentation]. :-)
 ## Relevant crates
 
 Other crates that might be useful in testing command line programs.
-* [dir-diff](https://crates.io/crates/dir-diff) for testing file side-effects.
-* [tempdir](https://crates.io/crates/tempdir) for scratchpad directories.
-* [duct](https://crates.io/crates/duct) for orchestrating multiple processes.
+* [dir-diff][dir-diff] for testing file side-effects.
+* [tempdir][tempdir] for scratchpad directories.
+* [duct][duct] for orchestrating multiple processes.
 
 ## License
 
@@ -91,5 +94,10 @@ submitted for inclusion in the work by you, as defined in the Apache-2.0
 license, shall be dual licensed as above, without any additional terms or
 conditions.
 
+[Travis]: https://travis-ci.org/killercup/assert_cli
+[Crates.io]: https://crates.io/crates/assert_cli
 [Documentation]: https://docs.rs/assert_cli
 [Environment]: https://github.com/Freyskeyd/environment
+[dir-diff]: https://crates.io/crates/dir-diff
+[tempdir]: https://crates.io/crates/tempdir
+[duct]: https://crates.io/crates/duct