본문으로 건너뛰기
cccskills
무료GitHub에 공개

audit

Full review of the claude-desktop-extra 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra스타 696(GitHub 696 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Audit - orchestrated project review

You are the coordinator. Spawn a team of sub-agents to review in parallel, then synthesize ONE report. Run from the repo root. $ARGUMENTS may scope the audit (e.g. "cowork only", "patches only"); default = full.

Use the AskUserQuestion tool (not limited to 4) whenever a finding needs the user's call. Read /architecture and /linux context first if unsure of the domain.

Pre-flight (you do this before fan-out)

  1. Ensure a fresh unpatched upstream extract exists for patch comparison: if ./tmp/app.asar.contents/.vite/build/index.js is missing or older than today, run /fresh-upstream (or tell the user and run the manual .deb crack + asar flow). Patches must be judged against the true current upstream, not a stale extract.
  2. Note .upstream-version vs the highest version in the official apt Packages index. Check ~/.config/Claude/logs/ exists for the log workstream.

Fan out - spawn these workstreams as parallel agents (Explore/general-purpose)

Give each agent the project path, the fresh-extract path, and ask for findings + file:line evidence + a recommended action, not file dumps.

  1. Patches vs upstream. For each patches/*/*.nim: does its target still exist in the fresh ./tmp bundle? Run ./scripts/validate-patches.sh ./tmp/app.asar.contents and report pass/fail. For failures, classify: pattern renamed / code refactored / feature removed / feature upstreamed (→ needs regression guard). Flag patches that may be vestigial (target gone, no longer needed) and gaps (new darwin/win32 gates with no Linux patch - diff process.platform old vs new). Verify EXPECTED_PATCHES strictness + no false-success idempotency (AGENTS.md Rule 6).
  2. Docs accuracy. Cross-check baseline/CLAUDE_FEATURE_FLAGS.md, CLAUDE_BUILT_IN_MCP.md, ION.md, PLATFORM_GATE_BASELINE.md, README.md patch table, and AGENTS.md against the actual current bundle + patches. Flag stale minified names, wrong counts, removed features still documented. (Read CHANGELOG.md head only: offset 1, limit 60.)
  3. Linux compatibility. Walk the support matrix (X11, Wayland-wlroots, Wayland-GNOME, Wayland-KDE, XWayland) × (Arch/Ubuntu/Debian/Fedora/RHEL/NixOS/Jetson, x86_64+aarch64). Check input (js/cu_linux_executor.js, executor_linux.js) + screenshot cascades still cover each session, the glibc floor (2.34 overall; kwin-portal-bridge 2.39) holds, launcher session detection is sound. Surface edge cases (ydotoold version, Niri, immutable distros, sandboxed/portal identity).
  4. Cowork backend (bundled native VM). Cowork runs on the .deb's bundled native VM backend (cowork-linux-helper + virtiofsd + smol-bin + QEMU/OVMF; requires /dev/kvm). The old claude-cowork-service Go daemon is deprecated and out of scope. Verify the Cowork-related patches/*/*.nim still match their targets in the fresh ./tmp bundle and that any regression guards still assert the upstreamed behavior. Flag drift against the current bundle.
  5. Runtime logs (if present). Scan ~/.config/Claude/logs/{main,cowork_vm_node,mcp,claude.ai-web}.log for errors/exceptions, permission denials, dispatch bridge issues (DISPATCH-FWD/DISPATCH-TRANSFORM), and renderer crashes. cowork_vm_node.log is the bundled backend's Electron-side log (still valid). Defer deep dispatch/cowork debugging to /debug.

Synthesize (you, after agents return)

Produce a report:

  • Summary table: workstream → status (clean / needs attention / broken) → headline finding.
  • Patches: vestigial (removable), at-risk (pattern drift), gaps (new Linux opportunities), each with file:line + recommended action.
  • Docs: what's stale + the exact fix.
  • Linux matrix: any session/distro/arch combo at risk.
  • Logs: notable errors + likely cause.
  • Solution approaches: ranked, with effort estimate. Use AskUserQuestion for any decision (delete a patch? add one? change behavior per backend?). When findings amount to upstream drift (stale patterns, new gates, protocol mismatch), the remediation path is /update - point there for the structured fix workflow.

Cross-reference memory (~/.claude/projects/-home-patrickjaja-development-claude-desktop-extra/memory/) for prior decisions before recommending changes. This is read-only review - propose, don't apply (unless the user then asks).

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

3p

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra6962026년 10월 26일 업데이트

architecture

무료

Explains the purpose, features, and architecture of claude-desktop-extra - 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra6962026년 10월 26일 업데이트

check-issue

무료

Take one or more claude-desktop-extra GitHub bug reports from triage to a shipped fix - read, classify ours vs upstream, reproduce without touching the user's running app, spec with the maintainer, implement and review in parallel, verify live, commit, release, and close the loop with the reporter. Self-improving - every run ends by folding what it learned back into this file. Invoke as "/check-issue <issue numbers or URLs>".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra6962026년 10월 26일 업데이트

comment

무료

Draft (and after approval, post) a reply on a claude-desktop-extra GitHub issue in this project's house voice - short, factual, friendly, no self-blame and no speculation - ending in one copy-pasteable command block that asks the reporter for the evidence we still need. Invoke as "/comment <issue number>".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra6962026년 10월 26일 업데이트

debug

무료

Debug a problem in claude-desktop-extra 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>".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra6962026년 10월 26일 업데이트

deploy

무료

Trigger the claude-desktop-extra Build & Release GitHub Actions pipeline (build-and-release.yml). With no argument the skill inspects the changes since the last release and decides force_rebuild itself; "/deploy force" / "/deploy no-force" override.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

patrickjaja/claude-desktop-extra6962026년 10월 26일 업데이트

patrickjaja의 스킬 모두 보기

이 스킬의 문제 신고