upgrade

Query GitHub releases and execute installer scripts to update the codegg agent.

Updated May 6, 2026
One-click install
npx skills add https://github.com/dbowm91/codegg --skill upgrade-dbowm91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/dbowm91/codegg/tree/main/.opencode/skills/upgrade
Command: npx skills add https://github.com/dbowm91/codegg --skill upgrade-dbowm91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of checking for and applying updates to the codegg agent, ensuring users always have access to the latest features and security patches without manual intervention.

Core Features & Use Cases

  • Version Discovery: Automatically queries the GitHub API to compare the current local version against the latest release.
  • Automated Installation: Triggers the official installer script to apply updates when a newer version is detected.
  • Use Case: A developer wants to ensure their coding agent is up-to-date before starting a new project; they can use this skill to verify the current status and perform an upgrade if necessary.

Quick Start

Run the upgrade command to check for available updates and apply the latest version of the codegg agent.

Frequently Asked Questions about upgrade

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

FAQPage Schema
How do I automate versioning and upgrade my CLI agent to the latest release?

Automating versioning and upgrading your CLI agent involves querying the GitHub API to compare local and remote versions, then executing a remote installation script to apply the latest binary update securely.

What is the process for checking codegg version parity against GitHub releases?

Checking codegg version parity involves querying the GitHub API to fetch the latest release metadata and comparing it against the current local installation to determine if an update is required.

Do I need network access and execution permissions to run automated CLI maintenance updates?

Yes, automated CLI maintenance updates require network access to the GitHub API to fetch releases and local execution permissions to run the official installer script for applying binary updates.

When should I use an automated upgrade script instead of manual maintenance for my coding agent?

You should use an automated upgrade script when you want to seamlessly verify version parity and apply security patches or new features without manual intervention, ensuring your coding agent is up-to-date.

Why does the automated upgrade process need to execute a remote installation script?

The automated upgrade process executes a remote installation script to securely overwrite the local binary with the newer version fetched from GitHub, ensuring the agent's environment is fully updated.