outdated

Identify major dependency upgrades and compile migration recommendations into tmp/UPGRADES.md.

Updated Sep 12, 2021
One-click install
npx skills add https://github.com/cerico/macfair --skill outdated
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: outdated
Source: https://github.com/cerico/macfair/tree/main/files/claude/skills/outdated
Command: npx skills add https://github.com/cerico/macfair --skill outdated

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes major version upgrades and generates migration recommendations, helping maintainers plan safer upgrades and minimize disruption.

Core Features & Use Cases

  • Identify major upgrades across a repository and surface affected packages.
  • Assess stability and breakage risk for each potential upgrade.
  • Output migration guidance to tmp/UPGRADES.md for tracking decisions and changes.

Quick Start

  • Run pnpm outdated to identify packages with major version changes.
  • Read existing tmp/UPGRADES.md if it exists (preserve previous decisions/notes).
  • For each major version upgrade, assess stability, breaking changes, and migration effort.
  • Write findings to tmp/UPGRADES.md

Frequently Asked Questions about outdated

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

FAQPage Schema
How do I identify major version upgrades for pnpm project dependencies?

To identify major version upgrades for pnpm project dependencies, run pnpm outdated to surface packages with major version changes, assess their stability and breaking change risks, and compile the findings into tmp/UPGRADES.md.

How do I assess the risk of breaking changes before a major dependency migration?

Risk assessment for breaking changes involves analyzing package stability and migration effort, evaluating compatibility across multiple packages, and documenting structured upgrade recommendations in tmp/UPGRADES.md.

What's the best way to track dependency migration decisions for a repository maintenance workflow?

The best way to track dependency migration decisions is consolidating stability assessments, compatibility evaluations, and structured guidance into a single report at tmp/UPGRADES.md, preserving previous notes for repository maintenance workflows.

Does this dependency migration tool require a specific package manager?

It requires pnpm to identify packages with major version changes, operating within repository maintenance workflows where teams evaluate breaking changes and compatibility across multiple packages.

What happens to previous upgrade notes when generating a new major version migration report?

When generating a new report, the tool reads existing tmp/UPGRADES.md if it exists to preserve previous decisions and notes, appending new major version upgrade findings alongside them.