dev-dependency

Audit and update NuGet and npm dependencies across full-stack projects.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-dependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-dependency
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/dev-dependency
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of tracking and updating dependencies across mixed-stack projects by providing a single, intelligent entry point for both NuGet and npm ecosystems.

Core Features & Use Cases

  • Automated Detection: Automatically identifies the package manager (NuGet or npm) based on project files or configuration.
  • Unified Workflow: Executes sequential updates for backend and frontend stacks, ensuring consistent dependency health.
  • Use Case: When you need to perform a security audit or upgrade packages across a full-stack application, this skill handles the detection, reporting, and execution of updates for both NuGet and npm in one command.

Quick Start

Invoke the dev-dependency skill to audit and update all project packages across both backend and frontend stacks.

Frequently Asked Questions about dev-dependency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate security patching for both npm and NuGet dependencies in a full-stack project?

Automated security patching for npm and NuGet dependencies is handled by detecting package managers from project files and executing synchronized backend and frontend updates through a unified command interface.

Can I update NuGet and npm packages at the same time to keep full-stack dependencies synchronized?

Yes, you can update NuGet and npm packages simultaneously by executing sequential updates for both backend and frontend stacks, ensuring consistent dependency health across the entire full-stack environment.

What is the best way to audit project dependencies across mixed technology stacks?

Auditing project dependencies across mixed stacks requires a unified workflow that automatically identifies the package manager and generates reports for both npm and NuGet ecosystems in one operation.

How do I detect which package manager a full-stack project is using before running an upgrade?

Package manager detection is automated by reading project files and configuration, identifying whether npm or NuGet is required before applying version upgrades and security patches.

Does this dependency update approach work for both frontend and backend environments?

Yes, this dependency update approach works for both frontend and backend environments, applying version upgrades and automated security patching to npm and NuGet packages respectively.