pre-commit by design operates on files, it also is optimized to batch runs of linters against files into multiple processes

what's happening here is your configuration is running several invocations (~1 per processor) of bash -c "cd bar && flake8" file1 file2 file3 etc. etc.

fortunately there's a setting you can use to fix this for you:

• pass_filenames: false

with that:

---
repos:
  - repo: local
    hooks:
      - id: flake8-foo
        name: Run flake8 in foo package
        entry: bash -c "cd foo && flake8"
        language: python
        pass_filenames: false
        files: ^foo/
        types: [python]
      - id: flake8-bar
        name: Run flake8 in bar package
        entry: bash -c "cd bar && flake8"
        language: python
        pass_filenames: false
        files: ^bar/
        types: [python]

that said, you're losing most of the benefits of the framework by going to a repo: local hook:

• pre-commit isn't managing the installation of the tools (each of your developers has to install the tool separately and at a particular version)
• any filename-based optimizations aren't happening
  • if you only change one file, you're currently linting your whole repository twice
  • during merge conflicts, pre-commit optimizes which files to run (not the whole repo)
  • and more

what I'd suggest instead for your monorepo setup is to still call flake8 in the normal way but utilize --config such that it works against your sub-repos:

repos:
-   repo: https://gitlab.com/pycqa/flake8
    rev: 3.8.4
    hooks:
    -   id: flake8
        name: flake8 ./foo/
        alias: flake8-foo
        files: ^foo/
        args: [--config, foo/setup.cfg]
    -   id: flake8
        name: flake8 ./bar/
        alias: flake8-bar
        files: ^bar/
        args: [--config, bar/setup.cfg]

disclaimer: I'm the author of pre-commit and the current maintainer of flake8

disclaimer: I'm the author of two of the tools in question (pre-commit, flake8-typing-imports) and the maintainer of the other (flake8)

the TYP005 code comes from flake8-typing-imports

there are two options for indicating your minimum supported version to flake8-typing-imports, the first is a command line argument / flake8 setting:

--min-python-version 3.6.1

or in your flake8 configuration

[flake8]
min_python_version = 3.6.1

if you're distributing a library, you can indicate the minimum supported version using the python_requires metadata -- this is specified in setup.cfg

[options]
python_requires >= 3.6.1

an aside, I believe there's some information missing from your question, without additional_dependencies in your pre-commit configuration, flake8 will be installed in isolation and won't have access to plugins such as flake8-typing-imports -- my guess is you've actually got a configuration similar to:

-   repo: https://gitlab.com/pycqa/flake8
    rev: 3.7.9
    hooks:
    -   id: flake8
        additional_dependencies: [flake8-typing-imports==1.9.0]

when speaking of command line arguments above, you could specify them as args here (though I personally prefer the configuration file approaches)

    -   id: flake8
        args: [--min-python-version, '3.6.1']
        additional_dependencies: [flake8-typing-imports==1.9.0]