productionos-update

Update ProductionOS plugins to the latest GitHub release across installations.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: productionos-update
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/productionos-update
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill keeps the ProductionOS plugin aligned with the latest release from GitHub, eliminating manual update drudgery and version drift across environments.

Core Features & Use Cases

  • Automates the end-to-end update workflow: detect current installation, fetch the latest changes, and apply updates.
  • Synchronizes updates across Marketplace, Codex plugin, and command files to ensure consistent behavior in both Codex and Claude contexts.
  • Supports rollback and verification steps to restore a previous version if an issue is detected.

Quick Start

Run the productionos-update skill to fetch and apply the latest version from GitHub.

Frequently Asked Questions about productionos-update

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

FAQPage Schema
How do I update the ProductionOS plugin to the latest GitHub release?

Updating ProductionOS detects the current version, fetches changes from origin/main, shows the changelog, and applies the update while syncing across all local, marketplace, and Codex plugin installations for consistent behavior.

How does version synchronization work across different ProductionOS installations?

Version synchronization applies cross-install mirroring to ensure the latest GitHub release is consistently applied across Marketplace, Codex plugin, and command files, eliminating version drift between Claude and Codex contexts.

Can I rollback a ProductionOS update if the latest version causes issues?

Yes, you can rollback a ProductionOS update. The skill supports rollback and verification steps to restore a previous version if an issue is detected after applying the latest GitHub release to your installations.

What is the best way to review changelog updates before applying a plugin synchronization?

The best way to review changelog updates is to run the update workflow, which automatically detects the current version, fetches updates from GitHub, and displays the changelog for review before applying the synchronization across all installations.

Do I need a specific environment to automate ProductionOS version updates across installations?

You need an existing ProductionOS installation to automate updates. The skill handles local, Marketplace, and Codex plugin installations by fetching updates directly from the origin/main branch on GitHub without requiring additional dependencies.