Analyzes and optimizes npm package dependencies. Handles outdated packages, npm audit findings, security vulnerabilities, dependency updates, unused dependency removal, and devDependencies recategorization. Recommends the lt-dev:npm-package-maintainer agent via /maintain commands. Activates for "update packages", "npm audit", "check dependencies", "security fix", or package.json optimization. NOT for @lenne.tech/nest-server version updates (use nest-server-updating).
Install
npx skillscat add lennetech/claude-code/maintaining-npm-packages Install via the SkillsCat registry.
NPM Package Maintenance
When to Use This Skill
- User mentions outdated packages or wants to update dependencies
- Security vulnerabilities found via
npm audit - Need to optimize
dependenciesvsdevDependencies - Removing unused packages from
package.json - Pre-release or post-feature dependency cleanup
- General package maintenance or housekeeping tasks
For comprehensive npm package maintenance, use the lt-dev:npm-package-maintainer agent via the maintenance commands.
Skill Boundaries
| User Intent | Correct Skill |
|---|---|
| "Update npm packages" | THIS SKILL |
| "npm audit fix" | THIS SKILL |
| "Remove unused dependencies" | THIS SKILL |
| "Update nest-server to v14" | nest-server-updating |
| "Fix NestJS service" | generating-nest-servers |
Related Skills
generating-nest-servers- For NestJS development when dependencies affect the serverusing-lt-cli- For Git operations after maintenancenest-server-updating- For updating @lenne.tech/nest-server (uses this agent internally)
Available Commands
| Command | Mode | Use Case |
|---|---|---|
/lt-dev:maintain |
FULL | Complete optimization (remove unused, recategorize, update all) |
/lt-dev:maintain-check |
DRY-RUN | Analysis only - see what would be done without changes |
/lt-dev:maintain-security |
SECURITY | Fast security-only updates (npm audit vulnerabilities) |
/lt-dev:maintain-pre-release |
PRE-RELEASE | Conservative patch-only updates before a release |
/lt-dev:maintain-post-feature |
FULL | Clean up after feature development |
When to Recommend Each Command
/lt-dev:maintain (FULL MODE)
Recommend when user wants:
- Complete dependency optimization
- General maintenance / housekeeping
- "Clean up my dependencies"
- "Update all packages"
/lt-dev:maintain-check (DRY-RUN)
Recommend when user wants:
- To see what would change without making changes
- Analysis or audit of current state
- "What packages are outdated?"
- "Check my dependencies"
- Pre-approval before making changes
/lt-dev:maintain-security (SECURITY-ONLY)
Recommend when user mentions:
npm auditvulnerabilities- Security issues
- CVEs or security advisories
- "Fix security vulnerabilities"
- Quick/urgent security fixes
/lt-dev:maintain-pre-release (PRE-RELEASE)
Recommend when user mentions:
- Preparing for a release
- "Before release"
- Wanting minimal/safe changes only
- Risk-averse updates
/lt-dev:maintain-post-feature (POST-FEATURE)
Recommend when user:
- Just finished implementing a feature
- Added new dependencies
- Wants to clean up after development work
What the Agent Does
The lt-dev:npm-package-maintainer agent performs 3 priorities:
- Remove unused packages - Finds and removes packages not used in the codebase
- Optimize categorization - Moves dev-only packages to devDependencies
- Update packages - Updates to latest versions with risk-based approach
All operations ensure npm run build and npm test pass before completion.
Quick Guidance
- User unsure? → Recommend
/lt-dev:maintain-checkfirst (safe, no changes) - Security urgent? → Recommend
/lt-dev:maintain-security(fast, focused) - Before release? → Recommend
/lt-dev:maintain-pre-release(conservative) - General cleanup? → Recommend
/lt-dev:maintain(comprehensive)