Configure tasks.json

Set up tasks.json so I can run unit tests with a single command. Create a task named RunTests that runs python -m pytest in the workspace root, shows output in the integrated terminal, and depends on a Prettier formatting step that runs only if files are staged. Save tasks.json in .vscode and make sure the task is available from the Run Task menu and bound to Ctrl+Alt+T.

Before I save tasks.json for the team's repo, make the task easy to review: put the test command and working directory up front, show the exact problemMatcher used for pytest, flag any environment variables or virtualenv assumptions, and point out anything that will break on CI versus local development. Suggest two small edits so a reviewer in procurement or ops can approve it quickly.

I added a RunTests task to tasks.json that runs python -m pytest, but invoking it reports command not found. I used the workspace's Terminal and I don't know if the task picks up my virtual environment, my shell PATH, or the correct working directory. I can't tell whether the task runner failed to inherit my activated venv or whether task.json syntax is wrong. What is the most likely diagnosis and the minimal steps to fix this for a dev on macOS using pyenv?

Across five projects I keep recreating tasks.json entries for linting, formatting, and running tests. Each dev has a different shell and virtualenv setup, which leads to inconsistent behavior. I want to stop spending half a day per repo on task config. What habit should I change first to standardize tasks.json and reduce onboarding friction for new team members?