Curate tests and decompose dependencies
yoinkskillsetup L2★381
majiayu000/claude-skill-registry ↗What it does
Decompose Python package dependencies via test-driven extraction
Best for
Understanding the minimal surface area of a Python library by running its tests in isolation, then progressively stripping away transitive dependencies to identify core requirements.
Inputs
- · GitHub URL or package name
- · Optional: PACKAGE_NAME override, skip test discovery flag
Outputs
- · Dependency graph
- · Test extraction results
- · Rewritten test imports
Requires
- · Python package tooling
- · Test discovery framework
- · Git (for cloning)
Preconditions
- · Target is a Python package (validation enforced)
- · GitHub repo or PyPI package accessible
- · Python environment with test framework support
Failure modes
- · Non-Python package input (rejected immediately)
- · Repo clone fails
- · Test discovery or import rewriting fails
- · Dependency resolution incomplete
Trust signals
- · Python-only validation enforced upfront
- · Three-phase pipeline (setup → curate → decompose) documented
- · Test framework integration explicit