update-minor-deps

Batch update non-breaking devDependencies in JavaScript monorepos with npm.

47|14|Updated Jan 8, 2020
One-click install
npx skills add https://github.com/makeup/makeup-js --skill update-minor-deps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-minor-deps
Source: https://github.com/makeup/makeup-js/tree/main/.claude/skills/update-minor-deps
Command: npx skills add https://github.com/makeup/makeup-js --skill update-minor-deps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating dev dependencies one-by-one is time-consuming, creates messy commit history, and risks accidentally mixing breaking changes into non-breaking update batches.

Core Features & Use Cases

  • Batch non-breaking updates: Groups all patch and minor devDependency version bumps into a single commit to keep project history clean and easy to bisect.
  • Built-in validation gates: Automatically runs build and test suites after updates to catch regressions before any changes are committed.
  • Supply-chain compliant: Handles registry-blocked or policy-rejected versions gracefully without bypassing corporate security controls.
  • Use Case: For a JavaScript monorepo with dozens of dev dependencies, use this skill to update all non-breaking versions at once, verify the build and tests pass, and create a single signed commit without manual effort.

Quick Start

Use the update-minor-deps skill to update all non-breaking dev dependencies for the current project, run build and tests, and create a signed commit if everything passes.

Frequently Asked Questions about update-minor-deps

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

FAQPage Schema
How do I batch update non-breaking devDependencies in a JavaScript monorepo?

Batch updating non-breaking devDependencies in a JavaScript monorepo involves grouping all patch and minor version bumps into a single commit. This skill automates the process, validates build and test suites, and generates a GPG-signed conventional commit if all checks pass.

What is the best way to update npm dev dependencies without introducing breaking changes?

The best way to update npm dev dependencies without breaking changes is to target only patch and minor versions. This skill enforces build and test pass gates after bumping versions to catch regressions before any dependency changes are committed to the project.

How does this dependency update process handle registry-blocked versions under supply-chain policies?

Handling registry-blocked versions under supply-chain policies means gracefully skipping rejected dependency updates without bypassing corporate security controls. The skill respects supply-chain compliance by validating versions against registry policies before applying any dev dependency updates.

Can I run build and test validation gates before committing dev dependency updates?

Yes, you can run build and test validation gates before committing dev dependency updates. The skill automatically executes build and test suites after applying version bumps, ensuring no regressions are introduced before creating a signed conventional commit for the tracked changes.

Does this skill work with npm projects that require GPG-signed conventional commits?

Yes, this skill works with npm projects requiring GPG-signed conventional commits. It automatically generates GPG-signed conventional commits for tracked dependency changes after verifying that build and test validation gates pass successfully.