check-updates

Checks Docker, Python, git, and npm components for updates and applies safe upgrades with rollback.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill check-updates-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-updates
Source: https://github.com/Wizarck/nexandro/tree/main/skills/check-updates
Command: npx skills add https://github.com/Wizarck/nexandro --skill check-updates-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a multi-component stack (Docker containers, Python packages, git repositories, npm modules) up to date requires manually checking each source, which is error-prone and often skipped, leaving systems outdated or broken by unsafe upgrades. ## Core Features & Use Cases - Stack-wide update detection: Scans Docker images, Python packages, git repositories, desktop apps, and npm modules for available updates in one run. - Safe apply with fallback: Runs the checker with --apply to perform updates, automatically falling back to a dry-run if the apply command fails. - Formatted reporting: Parses the JSON output into a concise, WhatsApp-friendly summary showing only components that are not up to date. - Use Case: A self-hosted stack operator asks the assistant to check for updates each morning; the Skill runs the checker script, applies safe updates, and returns a per-component report with upgrade commands for anything pending. ## Quick Start Ask the assistant to check the ELIGIA stack for outdated components and apply any safe updates, then show a summary report.

Frequently Asked Questions about check-updates

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

FAQPage Schema
How do I check Docker, Python, and npm components for updates at once?▼

Run the check-updates script, which scans Docker images, Python packages, git repositories, and npm modules in a single pass. It outputs JSON listing each component's status, which is then formatted into a summary report.

How to safely apply stack updates with automatic fallback?▼

The script runs with the --apply flag to perform updates directly. If that command fails, the workflow retries without --apply as a dry-run, so you still get the update report without risking a broken state.

What happens if the update checker script is missing?▼

The workflow first resolves the script path from the ONEDRIVE_PATH and ELIGIA_DIR environment variables and verifies the file exists. If it does not, it prints an error and stops instead of attempting to run anything.

Does the update report show components that are already current?▼

No, the summary only includes components whose status is not up_to_date. If everything is current, it returns a single confirmation message stating the whole stack is up to date.

Why does the update check fail on Windows paths?▼

Failures usually come from unset ONEDRIVE_PATH or ELIGIA_DIR environment variables, which are used to locate the checker script. Set these variables or ensure the defaults match your installation layout.