원클릭으로 Manus에서 모든 스킬 실행

deploy

스타543

포크32

업데이트2026년 7월 1일 02:30

Trigger the claude-desktop-bin Build & Release GitHub Actions pipeline (build-and-release.yml). Default run does not force; "/deploy force" sets force_rebuild=true to release even when the upstream version is unchanged (bumps pkgrel).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

patrickjaja

patrickjaja/claude-desktop-bin

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Deploy - trigger Build & Release

Args: $ARGUMENTS (only the literal word force is meaningful; anything else → non-force run).

Context

Repo: patrickjaja/claude-desktop-bin · Workflow: build-and-release.yml · default branch: master.
Current branch: !git -C /home/patrickjaja/development/claude-desktop-bin branch --show-current
Tracked upstream version: !cat /home/patrickjaja/development/claude-desktop-bin/.upstream-version 2>/dev/null
Recent runs: !gh -R patrickjaja/claude-desktop-bin run list --workflow=build-and-release.yml --limit 3 2>/dev/null || echo "(gh not ready)"

The workflow has one workflow_dispatch input: force_rebuild (boolean, default false). workflow_dispatch always runs the full pipeline (build → package deb/rpm/appimage/pkgbuild/nix → release → deploy-rpm-repo → deploy-pages). force_rebuild=true releases even if upstream is unchanged (bumps pkgrel for patch/feature-only updates).

Steps

Decide force: if $ARGUMENTS (trimmed, lowercased) equals force → FORCE=true, else FORCE=false.
Print a one-line plan: "Triggering build-and-release.yml on master (force_rebuild=)". (The pipeline ignores branch for dispatch; it builds against the latest official .deb and the committed tree on the default branch.)

Fire it (no interactive confirmation - the user already typed /deploy):

gh -R patrickjaja/claude-desktop-bin workflow run build-and-release.yml -f force_rebuild=<FORCE>

Wait ~3s, then resolve the run and report its URL:
```
gh -R patrickjaja/claude-desktop-bin run list --workflow=build-and-release.yml --limit 1 \
  --json databaseId,url,status,event,createdAt
```
Report the run URL and status. Offer: "Watch with gh -R patrickjaja/claude-desktop-bin run watch <id>".

Notes

Non-force is the default and is correct for a normal new-upstream release (after .upstream-version was bumped). Use force for patch/feature changes where upstream version did not move.
Do NOT bump versions or edit files here - this only triggers the pipeline. Version/patch work belongs in /update.
If gh workflow run errors with "Workflow does not have 'workflow_dispatch'" it's a permissions/branch issue - confirm the workflow file on master still declares workflow_dispatch.

이 저장소의 다른 Skills

같은 저장소

update

patrickjaja/claude-desktop-bin

For claude-desktop-bin - handle a new upstream Claude Desktop version end-to-end: build, fix failing patches, diff old vs new JS for new platform gates, audit feature flags + ion-dist + platform gates, update baseline docs + CHANGELOG, bump .upstream-version, then commit. Mirrors issue #145 / UPDATE-PROMPT-CC-INPUT-MANUAL.md.

2026-07-11543

linux

patrickjaja/claude-desktop-bin

Linux compatibility reference for the claude-desktop-bin project (repackaging Anthropic's official Claude Desktop Linux .deb and patching its app.asar for the distros Anthropic does not ship). Use when working on Linux support, session managers, distros, Computer Use input/screenshot backends, glibc floors, Wayland/X11, multi-profile, or any patch in patches/*.nim. Loads the distro/session matrix, the input + screenshot cascades, native-binary glibc floors, and known Linux gotchas.

2026-07-08543

patrickjaja/claude-desktop-bin

Reference for the 3p / enterprise / inference-gateway deployment of Claude Desktop on Linux - how /etc/claude-desktop/managed-settings.json is read, what "3p mode" changes (separate ~/.config/Claude-3p userData, hidden Chat tab, the false VM-download banner), how Cowork still runs under it, which hardcoded paths are safe vs split under the -3p switch, and how to verify it all from logs. Use when working on managed-settings.json, inferenceProvider/gateway/Bedrock/Vertex configs, the 3p setup SPA (ion-dist), the Claude-3p directory, or debugging managed-deployment Cowork.

2026-07-01543

architecture

patrickjaja/claude-desktop-bin

Explains the purpose, features, and architecture of claude-desktop-bin - which repackages Anthropic's official Claude Desktop Linux .deb for Arch/Fedora/RHEL/Nix/AppImage and layers Linux-only extras (Computer Use, themes, multi-profile, Quick Entry) on top via surgical JS patches. Use when onboarding, writing docs/READMEs, explaining what the project does, or reasoning about how the official build and our patches fit together.

2026-07-01543

audit

patrickjaja/claude-desktop-bin

Full review of the claude-desktop-bin project - patches vs the official Linux .deb (still needed? new ones needed? did the surrounding code change?), docs accuracy, Linux compatibility across the distro/session matrix, and runtime logs. Orchestrates a team of sub-agents and produces a consolidated report with solution approaches.

2026-07-01543

debug

patrickjaja/claude-desktop-bin

Debug a problem in claude-desktop-bin by pulling the right local evidence - the most recent local-agent-mode session transcript (your last prompt + the model's tool calls/errors) and the Claude Desktop logs - and asking you for anything else worth collecting for the specific issue. Invoke as "/debug <short description of what's broken>".

2026-07-01543

name	deploy
description	Trigger the claude-desktop-bin Build & Release GitHub Actions pipeline (build-and-release.yml). Default run does not force; "/deploy force" sets force_rebuild=true to release even when the upstream version is unchanged (bumps pkgrel).
disable-model-invocation	true
argument-hint	[force]
allowed-tools	Bash(gh workflow run ), Bash(gh run list ), Bash(gh run view ), Bash(gh workflow view )

Deploy - trigger Build & Release

Args: $ARGUMENTS (only the literal word force is meaningful; anything else → non-force run).

Context

Repo: patrickjaja/claude-desktop-bin · Workflow: build-and-release.yml · default branch: master.
Current branch: !git -C /home/patrickjaja/development/claude-desktop-bin branch --show-current
Tracked upstream version: !cat /home/patrickjaja/development/claude-desktop-bin/.upstream-version 2>/dev/null
Recent runs: !gh -R patrickjaja/claude-desktop-bin run list --workflow=build-and-release.yml --limit 3 2>/dev/null || echo "(gh not ready)"

Steps

Decide force: if $ARGUMENTS (trimmed, lowercased) equals force → FORCE=true, else FORCE=false.
Print a one-line plan: "Triggering build-and-release.yml on master (force_rebuild=)". (The pipeline ignores branch for dispatch; it builds against the latest official .deb and the committed tree on the default branch.)

Fire it (no interactive confirmation - the user already typed /deploy):

gh -R patrickjaja/claude-desktop-bin workflow run build-and-release.yml -f force_rebuild=<FORCE>

Wait ~3s, then resolve the run and report its URL:
```
gh -R patrickjaja/claude-desktop-bin run list --workflow=build-and-release.yml --limit 1 \
  --json databaseId,url,status,event,createdAt
```
Report the run URL and status. Offer: "Watch with gh -R patrickjaja/claude-desktop-bin run watch <id>".

Notes

Non-force is the default and is correct for a normal new-upstream release (after .upstream-version was bumped). Use force for patch/feature changes where upstream version did not move.
Do NOT bump versions or edit files here - this only triggers the pipeline. Version/patch work belongs in /update.
If gh workflow run errors with "Workflow does not have 'workflow_dispatch'" it's a permissions/branch issue - confirm the workflow file on master still declares workflow_dispatch.