update

Update claude-desktop-bin packaging for a new upstream Claude Desktop release.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill update-patrickjaja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/patrickjaja/claude-desktop-bin/tree/main/.claude/skills/update
Command: npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill update-patrickjaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the recurring work of moving claude-desktop-bin to a new upstream Claude Desktop release, so packaging stays current without manual guesswork.

Core Features & Use Cases

  • End-to-End Release Update: Rebuild the package against the latest upstream release, repair broken patches, and verify the result.
  • Compatibility Audits: Check for new Linux platform gates, feature-flag changes, ion-dist regressions, and cowork-service cross-dependencies.
  • Documentation and Version Sync: Update the changelog, baseline notes, patch references, and the upstream version marker so the repository reflects the new release.
  • Use Case: A maintainer can run this Skill when Claude Desktop ships a new version and needs a clean, tested, documented Linux package update.

Quick Start

Use the update skill to prepare claude-desktop-bin for the latest upstream release, fix any broken patches, audit Linux compatibility, and update the version and changelog.

Frequently Asked Questions about update

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

FAQPage Schema
How do I update a Linux package when a new upstream release ships?

To update a Linux package for a new upstream release, you extract the latest source, validate existing patches, bump the version marker, synchronize the changelog, and sequence safe commit-and-deploy steps to keep the build functional.

How do I audit Linux compatibility after a Claude Desktop version bump?

A Linux compatibility audit checks for new platform gates, feature-flag changes, ion-dist regressions, and cowork-service cross-repository dependencies to ensure the version bump does not break existing functionality.

What is the best way to repair broken patches during a release rebuild?

Repairing broken patches during a release rebuild involves applying fresh upstream extraction, validating patch references against the new codebase, and updating baseline notes to maintain package buildability.

Do I need to synchronize the changelog and documentation when updating a Linux build?

Yes, you must synchronize the changelog, baseline notes, patch references, and upstream version marker so the repository accurately reflects the new release and maintains a clean build state.

What does end-to-end release engineering for a Linux package involve?

End-to-end release engineering involves rebuilding the package against the latest upstream release, repairing patches, auditing Linux gates, verifying ion-dist, reviewing cross-repository dependencies, and updating documentation safely.

Why does my Linux package build fail after an upstream version bump?

A Linux package build fails after an upstream version bump when existing patches break, new Linux platform gates block execution, or ion-dist regressions appear, requiring fresh extraction and patch validation.