Flake8

Define a strict .flake8 config for the team.

Add a 'flake8 .' step in the GitHub Actions YAML file.

Set the CI to fail if Flake8 returns a non-zero exit code.

Require all contributors to fix linting errors before merging.

Run Flake8 with all checks enabled.

Export results to a JSON file using a custom formatter.

Aggregate error counts to identify the most frequent violations.

Prioritize refactoring tasks based on error severity.

Set '--max-complexity 10' in the project configuration.

Run Flake8 across the repository.

Identify functions triggering 'C901' errors.

Refactor flagged functions into smaller sub-routines.

Install the 'flake8-bandit' plugin.

Run Flake8 normally.

Review 'S' prefixed error codes which indicate security vulnerabilities.

Patch vulnerabilities before deployment.

Install the 'flake8-docstrings' plugin.

Configure the tool to follow 'google' or 'numpy' docstring styles.

Run linting to find missing or malformed documentation.

Auto-generate or manually update missing docstrings.

Configure Flake8 with descriptive error messages.

Have junior developers run the linter locally.

Instruct them to research the specific PEP 8 rules for each triggered code.

Verify they understand the 'why' behind each correction.

Run Flake8 to identify syntax errors that might crash auto-formatters.

Fix critical syntax issues.

Run Black to format the code.

Run Flake8 again to ensure no formatting rules conflict with team standards.