adeel-upgrade

Upgrades Adeel installations with manual or automatic flows and changelog presentation.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/agwacom/adeel --skill adeel-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adeel-upgrade
Source: https://github.com/agwacom/adeel/tree/main/skills/adeel-upgrade
Command: npx skills add https://github.com/agwacom/adeel --skill adeel-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrades Adeel to the latest version and handles the distinction between global and vendored installs, ensuring the upgrade is performed safely and with visibility into changes.

Core Features & Use Cases

  • Manual trigger: invoke upgrade on demand with /adeel-upgrade.
  • Install-type detection: automatically detects global vs vendored installations and chooses the correct upgrade path.
  • Change log and state: shows "what's new" after upgrade and updates version markers for future references.

Quick Start

Type /adeel-upgrade to upgrade Adeel to the latest version.

Frequently Asked Questions about adeel-upgrade

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

FAQPage Schema
How do I upgrade a vendored installation to the latest version?

To upgrade a vendored installation, the system automatically detects your install type and safely routes the upgrade path, executing setup and saving version markers afterward to ensure your vendored environment is current.

What is the best way to automate version management for global-git installations?

Automating version management for global-git installations is handled by detecting the global install type and applying the correct upgrade flow, saving version markers and presenting a changelog summary upon completion.

Does the upgrade process work with both manual and automatic flows?

The upgrade process works with both manual and automatic flows, allowing you to invoke upgrades on demand while automatically detecting global, local, or vendored installation types to choose the correct path.

What happens to version markers and changelogs after an upgrade?

After an upgrade, version markers are saved for future references and a What's New summary is presented, giving you visibility into the changelog and state changes made during the installation update.

Can I use this to distinguish between global and vendored installs before upgrading?

You can distinguish between global and vendored installs because the system features automatic install-type detection, identifying whether you have a global-git, local-git, vendored, or vendored-global setup before executing the upgrade.