forbotsake-upgrade

Name: forbotsake-upgrade
Availability: InStock
Author: forbotsake

Detect git or vendored installs and upgrade forbotsake with changelog summaries.

5|1|Updated Apr 5, 2026

Search Tags:#automation #git #changelog #upgrade #version #vendored #forbotsake

Ready to run

npx skills add https://github.com/forbotsake/forbotsake --skill forbotsake-upgrade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: forbotsake-upgrade
Source: https://github.com/forbotsake/forbotsake/tree/main/forbotsake-upgrade
Command: npx skills add https://github.com/forbotsake/forbotsake --skill forbotsake-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps your forbotsake installation up-to-date by automatically upgrading to the latest release, detecting whether the install is git-based or vendored, and clearly showing what changed.

Core Features & Use Cases

Detects install type (git vs vendored) and applies the correct upgrade path.
Fetches the latest version, performs the upgrade, and verifies success.
Presents a changelog summary to help you review what's new before adopting the upgrade.

Quick Start

Run the forbotsake-upgrade upgrade flow to upgrade the installed version and show what changed.

Frequently Asked Questions about forbotsake-upgrade

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

FAQPage Schema

How do I upgrade forbotsake to the latest version safely?▼

To upgrade forbotsake safely, the tool detects your installation type and applies the appropriate upgrade path, fetching the latest version, performing the upgrade, and verifying success before finalizing.

How does the forbotsake upgrade process handle git versus vendored installations?▼

The upgrade process detects git installations to perform a fetch and reset, while vendored installations trigger a repository clone, ensuring the correct upgrade path is applied automatically based on your setup.

Can I see what changed before committing to a forbotsake version upgrade?▼

Yes, the upgrade flow presents a changelog summary by reading the CHANGELOG.md file, allowing you to review new changes and features before adopting the latest forbotsake version.

What do I need in my installation directory to run an automated forbotsake upgrade?▼

You need shell capabilities to run git commands or clone repositories, and your installation directory must contain the VERSION and CHANGELOG.md files to execute the automated forbotsake upgrade.

Does the forbotsake upgrade automation work for both local development and production deployments?▼

Yes, the forbotsake upgrade automation applies to both local development setups and production deployments, executing the necessary git or vendored operations to update the environment safely.

Why does my forbotsake version upgrade require shell access and specific directory files?▼

Shell access is required to execute git commands or clone repositories, while VERSION and CHANGELOG.md files are needed to determine the current version and generate the changelog summary for the upgrade.