TheAlgorithms/Python

8 other commands the scanner could not classify

Commands from CI steps and task runners that look like checks but match no known tool. Some are checks, some are not.

• pre-commit hook auto-walrus
• pre-commit hook matchify
• pre-commit hook pyproject-fmt
• pre-commit hook requirements-txt-fixer
• pre-commit hook rumdl
• pre-commit hook rumdl-fmt
• pre-commit hook validate-pyproject
• ty check --output-format=github --exit-zero

full scan as JSON

• Docstring StandardsApply a single documentation rule set across the codebase: - **Module/file docstring:** Each file should have a clear module-level docstr...

  TheAlgorithms/Python Documentation Python docs 2026-05-05

  copy raw open
• CI workflow correctnessAll CI workflows must be syntactically valid, reliably triggered, and logically non-redundant. Apply these rules: 1) Every step must be v...

  TheAlgorithms/Python CI/CD Yaml docs 2026-03-26

  copy raw open
• Validate Inputs ExplicitlyEnforce each function’s documented input contract with early, explicit checks; raise specific exceptions with accurate messages (avoid as...

  TheAlgorithms/Python Error Handling Python docs 2026-05-05

  copy raw open
• Automate All Behavior TestsFor every algorithmic change (and every public function/class), require automated tests that lock in both correctness and failure modes. ...

  TheAlgorithms/Python Testing Python docs 2026-05-02

  copy raw open
• Self-Documenting Naming RulesUse self-documenting identifiers: variable/function/class names should explain intent without relying on comments, and avoid confusing or...

  TheAlgorithms/Python Naming Conventions Python docs 2026-05-01

  copy raw open
• Pure Functions and Main GuardKeep reusable code clean and production-ready: reusable/algorithmic functions should be side-effect free (no `print()`), and all executab...

  TheAlgorithms/Python Code Style Python docs 2026-04-30

  copy raw open
• Algorithm Correctness StandardsWhen implementing algorithms, enforce correctness and reliability by following this checklist: 1) Validate stated preconditions (and docu...

  TheAlgorithms/Python Algorithms Python docs 2026-05-05

  copy raw open
• Performance-Sensitive EfficiencyWhen optimizing, watch for *hidden* inefficiencies: avoid O(n) per-step operations, don’t duplicate expensive work, and don’t eagerly mat...

  TheAlgorithms/Python Performance Optimization Python docs 2026-05-02

  copy raw open
• Explicit Optional NullsWhen a value can be absent, represent that absence explicitly and consistently. **Do** - Use `Optional[...]`/`T | None` in type hints for...

  TheAlgorithms/Python Null Handling Python docs 2026-04-29

  copy raw open
• Validate Security InputsSecurity-sensitive code should *fail fast* with explicit validation of inputs and security parameters. That means: (1) validate structure...

  TheAlgorithms/Python Security Python docs 2025-01-30

  copy raw open
• Avoid stray commasWhen running linters/formatters in CI or scripts, keep command arguments syntactically precise and standardized—remove any stray or meani...

  TheAlgorithms/Python Code Style Yaml docs 2025-08-23

  copy raw open
• Use semantic namesUse intention-revealing, consistent, and unique names for CI workflow, jobs, and steps (avoid generic labels like `build`). Names should ...

  TheAlgorithms/Python Naming Conventions Yaml docs 2025-08-23

  copy raw open
• Idiomatic Style CommandsWhen writing style guidance (including README/CONTRIBUTING snippets), keep examples concise and readable: 1) Use idiomatic tool invocatio...

  TheAlgorithms/Python Code Style Markdown docs 2024-10-05

  copy raw open