upgrade-dependencies

Upgrade npm dependencies and GitHub Actions with testing and verification.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill upgrade-dependencies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-dependencies
Source: https://github.com/tnez/docent/tree/main/.docent/skills/docent/upgrade-dependencies
Command: npx skills add https://github.com/tnez/docent --skill upgrade-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, git cli, gh cli, Node.js, jq.

What problem does it solve?

Outdated dependencies introduce security vulnerabilities, bugs, and compatibility issues. This Skill provides a controlled, manual process for upgrading npm dependencies and GitHub Actions, ensuring your project remains current, secure, and stable without the risks of fully automated updates.

Core Features & Use Cases

  • Outdated Dependency Check: Identifies all packages with available updates and security vulnerabilities.
  • Prioritized Upgrades: Guides through categorizing and prioritizing updates (security, production, dev, major versions).
  • Controlled Testing: Ensures thorough testing after each upgrade step to prevent regressions.
  • GitHub Actions Updates: Facilitates keeping CI/CD workflows current and compatible.
  • Use Case: It's time for your monthly dependency review. Use this Skill to systematically check for outdated packages, address security vulnerabilities first, upgrade production and development dependencies incrementally with testing, and update GitHub Actions, all while maintaining full control and stability.

Quick Start

Upgrade all outdated npm dependencies and GitHub Actions.

Frequently Asked Questions about upgrade-dependencies

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

FAQPage Schema
How do I identify outdated npm dependencies and security vulnerabilities in my project?

Use npm to identify outdated dependencies and security vulnerabilities. Run `npm outdated` to list packages with available updates and `npm audit` to detect known security issues. This Skill guides you through reviewing these results and prioritizing which updates to apply first based on security urgency and stability impact.

What's the best way to upgrade npm dependencies safely without breaking my project?

Upgrade npm dependencies incrementally by categorizing updates into security, production, and development groups, then test after each step. This Skill provides a controlled process that validates upgrades with npm audit and test runs before committing, preventing regressions and ensuring stability.

Can I automate updates to GitHub Actions workflows alongside npm dependencies?

Yes, this Skill covers updating both npm dependencies and GitHub Actions in a single controlled workflow. It guides you through identifying outdated actions, upgrading them systematically, and committing changes through a release process that maintains compatibility and stability.

When should I perform a monthly dependency review instead of letting updates happen automatically?

Manual dependency upgrades let you prioritize security vulnerabilities, test changes thoroughly, and maintain control over stability. This Skill is designed for monthly reviews or security-driven upgrades where you plan, group, test, and verify updates before committing, reducing the risk of automated drift.

Do I need Git and GitHub CLI installed to use this dependency upgrade process?

Yes, this Skill requires npm, Node.js, Git CLI, GitHub CLI, and jq to run. These tools enable checking for outdated packages, committing changes, and pushing updates through a controlled GitHub Actions workflow. Ensure they're installed in your environment before starting.

What happens if an npm dependency upgrade fails tests or conflicts with other packages?

This Skill includes testing and verification steps after each upgrade to catch failures early. If a major version upgrade causes conflicts, you can revert the change, skip that dependency for now, or address compatibility issues before attempting the upgrade again.