Install anti-slop-py

Install the three anti-slop-py layers into the current repository: ready-made Ruff rules, mypy strict flags, and the bundled Flake8 plugin carrying the custom ASP rules. Preserve unrelated work and adapt to the project's package manager and configuration style.

Choose the mode first

• Scan (no repo changes). The user wants findings, an audit, or explicitly asked not to touch the repository. Run the rules straight from this skill's bundled copy and report; write nothing to the target repo:

  uv run --with flake8 flake8 --config <skill-directory>/assets/configs/flake8-scan.ini src tests
  

  Complement with the ready-made layers as CLI flags, still with zero repo changes: uv run ruff check --extend-select ANN401,PGH003,B009,B010 src tests and, when a full type audit is wanted, uv run mypy --disallow-any-explicit --disallow-any-generics src. Drop ASD/ASF via --select ASP when the target has no pydantic/fastapi. Report findings grouped by rule with the suggested fix per group.

• Install (enforcement). The user wants the rules wired into the repository so CI and every developer runs them. Confirm this is wanted before changing files, then pick the flavor:

  • Package (default): add anti-slop-py as a development dependency with the repository's own manager (uv add --dev anti-slop-py). The entry points register the ASP rules automatically; create or merge a .flake8 with select = ASP, adding ,ASD,ASF plus enable-extensions = ASD,ASF when pydantic/fastapi is a direct dependency. Skip steps 2 and the [flake8:local-plugins] part of step 4 below; everything else in the procedure applies.
  • Vendored (only on explicit request): the user wants to own and edit the rules locally. Follow the full procedure below. Never combine both flavors in one repo; each finding gets reported twice.

Procedure