You might start using super-linter in a test workflow.

steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          fetch-depth: 0
          persist-credentials: false
      - name: Super Linter Code Base
        uses: github/super-linter/slim@v5
        env:
          FILTER_REGEX_INCLUDE: "/hexonet/*|/scripts/*|updateVersion.sh|setup.py"
          VALIDATE_PYTHON_BLACK: true
          # further linters on demand e.g. VALIDATE_BASH: true
          VALIDATE_ALL_CODEBASE: false
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

That is at least validating newly touched files using Black. It is not auto-reformatting. That's something you would to cover through your IDE the best (e.g. VSCode, ms-python.black-formatter extension).

You may dive into adding a .devcontainer folder with respective files (Dockerfile, devcontainer.json, ...) to add a Python-based Dev Container to have always a working environment at hand which is handy if you switch to another device. You just need docker. VSCode automatically starts the container up and you can directly develop in there.

All this is coming with some work, but worth it.