Add pylint docstrings to precommit hook

[Michael-T-McCann]

We current check for docstrings on PRs, but it would be nice to have this checked client-side as part of the precommit hook. This would also involve changing the dev requirements and updating the docs.

[SauravMaheshkar]

@bwohlberg Can I take this up ? I'd love to contribute to the repository and this seems like a nice "good first issue".

I'll make changes to the .pre-commit-config.yaml, the dev requirements and the docs.

[bwohlberg]

Thanks @SauravMaheshkar, that would be great.

[SauravMaheshkar]

Request for clarification: @bwohlberg In which section should I add pylint ? In the Tests section or the Contributing Code section ?

[bwohlberg]

The only existing reference I can find to the pre-commit hook is in point 9. of Installing a Development Version, so the minimal change necessary for consistency would seem to simply involve adding a mention of pylint to that paragraph.

@Michael-T-McCann: Any additional thoughts on this?

[Michael-T-McCann]

Unfortunately, the solution in #141 seems to run pylint on every file in the commit, including files that are normally skipped when running pylist scico. In particular, if your commit touches a test file, you now must add docstrings to all the tests before you can commit.

[bwohlberg]

Note also the --score=n added to .pre-commit-config.yaml in #143.