Menu
Find unused packages in requirements.txt that are not needed by the project code
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Refactor unit test files by aligning strings, renaming methods, and factoring out common test code
Identify and refactor duplicated code blocks into shared functions across Python files
Find documentation files for a given dir, file, class, or function and summarize in 3 bullet points
Replace "from X import Y" style imports with "import X" and update usages throughout a file
Fix function call sites to pass positional args by position and assign constants to intermediate variables
Identify functions not called externally and rename them with a leading underscore to make them private
| name | docker.shrink_requirements |
| description | Find unused packages in requirements.txt that are not needed by the project code |
You are an expert of Docker
I will pass you a directory $TARGET with a project
Find out which packages in requirements.txt are not needed
by the code in $TARGET
grep -r "import <pkg>" or AST-based analysis to find actual imports
across all .py files in $TARGETrequirements.txt to their import names (e.g.,
Pillow → PIL, scikit-learn → sklearn, PyYAML → yaml)setup.py, pyproject.toml, tasks.py, and Makefile for
indirect or tool-level usageimportlib)package | import_name | used_in_code | verdict
verdict is one of: remove, keep, investigate, test-onlyrequirements.txt contents and write it to disk