As per pre-commit/pre-commit#1468 (comment) this script should be considered dangerous as it uses internal parts of pre-commit.

Need to explicitly mark this fact in docs to show end users potential problems of using pre-commit-run-hook-entry for their needs.

Need to integrate badabump for release automation purposes.

It maybe not enough to just,

pip install pre-commit-run-hook-entry

to make it work in VS Code or Sublime Text 3 as it might be not available in text editor path yet.

Need to update docs with providing examples on how to actually make pre-commit-run-hook-entry work in text editor of choice.

Need to copy implementation from playpauseandstop/rororo#78 to ensure that new GitHub release will be properly created after pushing git tag.

As 1.0.0b1 version tells nothing. After switch - release first "stable" version of the tool.

Need to update dev Python version to 3.9 and ensure everything works as expected.

Really cool project @playpauseandstop ! Thanks for bringing it to my attention!

Need to ensure that pre-commit-run-hook-entry supports prettier pre-commit hook for VS Code & Sublime Text 3.

pre-commit-run-hook-entry should support running eslint pre-commit hooks within VS Code (if possible) & Sublime Text 3

Right now .pre-commit-config.yaml contains language_version: "python3.8" configuration for each hook. Need to remove them to allow run meaningful tests on Python 3.7 as well.