investigate-dependencies
Conduct thorough dependency audits to identify redundant code, unused features, and improper usage patterns. Examines each import to ensure we're leveraging existing capabilities rather than reinventing functionality.
npx skills add majiayu000/claude-skill-registry --skill investigate-dependencies-taylorsatula-mira-oss --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Investigate Dependencies: Eliminating Redundant Code Through Dependency Mastery ## 🎯 Mission Conduct line-by-line walkthroughs of modules to understand how we use external dependencies, identifying: - **Redundant implementations** of functionality that already exists in imported modules - **Unused capabilities** in dependencies that could simplify our code - **Improper usage patterns** that don't align with the module's intended design - **Missing error handling** for cases the dependency already covers ## 🔍 Investigation Protocol ### Step 1: Import Analysis For each file under investigation, create an import inventory: ```markdown ## Import Inventory for [filename] | Import | Source | Purpose | Documentation | |--------|--------|---------|---------------| | `uuid` | stdlib | Generate unique identifiers | https://docs.python.org/3/library/uuid.html | | `FastAPI` | fastapi | Web framework | https://fastapi.tiangolo.com/ | | `CustomUtil` | local | [Document what we think it does] | [Internal docs] | ``` ### Step 2: Line-by-Line Dependency Usage Examination For each location where an external module is used: ```markdown ### Usage Point: [Function/Method Name] (Lines X-Y) **Code:**
- 🎯 Mission
- 🔍 Investigation Protocol
- Step 1: Import Analysis
- Step 2: Line-by-Line Dependency Usage Examination
- Step 3: Documentation Deep Dive
- Step 4: Redundancy Detection
- Step 5: Capability Gap Analysis
- 📋 Investigation Template
- 🎯 Focus Areas
- Common Redundancy Patterns
- 🚨 Red Flags
- ✅ Success Criteria
- 📚 Investigation Request Format
- 🎓 Philosophy
What does the investigate-dependencies skill do?
Conduct thorough dependency audits to identify redundant code, unused features, and improper usage patterns. Examines each import to ensure we're leveraging existing capabilities rather than reinventing functionality.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill investigate-dependencies-taylorsatula-mira-oss --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.