gpsaggese/helpers / .claude/skills/docker.shrink_requirements
docker.shrink_requirements
VerifiedFind unused packages in requirements.txt not needed by the project code
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
SKILL.md
View on GitHub---
description: Find unused packages in requirements.txt not needed by the project code
model: haiku
---
# Goal
- Act as an expert in Docker
- Given a project dir `<TARGET_DIR>`, find the packages in `requirements.txt`
that its code does not need
# Workflow
## Methodology
- Find actual imports in all `.py` files in `<TARGET_DIR>` with
`grep -r "import <PKG>"` or AST-based analysis
- Map each package in `requirements.txt` to its import name (e.g., `Pillow` ->
`PIL`, `scikit-learn` -> `sklearn`, `PyYAML` -> `yaml`)
- Also check `setup.py`, `pyproject.toml`, `tasks.py`, and `Makefile` for
indirect or tool-level usage
- Flag but do NOT remove packages that are:
- Runtime plugins or extras loaded dynamically (e.g., via `importlib`)
- Transitive dependencies pulled in by other listed packages
- Used only in test files (mark them as "test-only")
## Output
- Print a table with columns:
```verbatim
package | import_name | used_in_code | verdict
```
- `verdict` is one of: `remove`, `keep`, `investigate`, `test-only`
- Propose the trimmed `requirements.txt` contents and write it to disk
# Verification
- [ ] Confirm every package in `requirements.txt` has a verdict
- [ ] Confirm no package marked `remove` is still imported anywhere in
`<TARGET_DIR>`
- [ ] Confirm the trimmed `requirements.txt` was written to disk
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |