Skip to content

lidge-jun/codexclaw / plugins/codexclaw/skills/dev-devops

cxc-dev-devops

Verified

Use for infra, CI/CD, releases, repo policy, worktree cleanup and native desktop apps. Triggers: Dockerfile, K8s, IaC, SRE, Tauri, 스택 PR CI, 배포, 인프라, 쿠버네티스, 브랜치 정리, 브랜치 삭제, 워크트리 정리, 저장소 세팅, 브랜치 보호, 에이전트 PR, PR 정책, 데스크톱 앱, 메뉴 막대.

references/cross-platform-release.md

View on GitHub
# Cross-platform Release — CI Matrix vs Local OS Proof

Last reviewed: 2026-06-21
Applies to: CLI packages, desktop-affecting releases, browser automation, installers, shell shims
When to read: Release claims include Linux/macOS/Windows support or local OS behavior
Canonical owner: dev-devops cross-platform release proof

---

## §1 Core Rule

CI systems such as GitHub Actions prove behavior inside their runner
environments. When a release claim depends on cross-platform local behavior that
CI cannot observe, recommend setting up the required target environment before
claiming release confidence.

Do not require direct desktop verification for every release. Require it only
when the release claim depends on OS-local behavior beyond CI's visibility.

## §2 Evidence Decision Table

| Release behavior | CI matrix enough? | Direct OS/UI verification? | Proof bundle |
|---|---:|---:|---|
| Pure library package | Usually yes | No | Test/import matrix |
| CLI binary wrapper/shim | Yes for core command behavior | Maybe for PATH/shell integration | Install, bin resolve, `--version`, `--help`, safe command |
| Browser automation/profile paths | Partial | Yes when local profile/app behavior matters | Runner smoke plus visible browser/profile proof |
| Desktop app or installer | No | Yes | Launch, permission prompt, install/uninstall evidence; full matrix in `native-desktop-acceptance.md` |
| Windows PATH/PowerShell/shim | Partial | Yes if release claim depends on Windows user behavior | Windows runner plus Windows App/RDP verification |
| macOS TCC/Keychain/app bundle | Partial | Yes | macOS runner plus visible macOS app/session proof; prompts in `macos-system-approvals.md` |
| YAML/cloud-only pipeline change | Yes | No | Static validation, CI dry run, API/provider check |

## §3 Mandatory Environment Prompt

When CI cannot prove required cross-platform local behavior, ask for the target
environment instead of pretending it was verified.

Use this shape:

> This release affects `<platform behavior>`. CI can cover `<runner evidence>`,
> but cannot prove `<local behavior>`. Please provide or open `<target
> environment>` if direct verification is required before release.

Examples:

- macOS runtime, Windows-local PATH/PowerShell behavior matters:
  ask the user to provide Windows App/RDP or another visible Windows
  environment.
- Linux/CI-only runtime, macOS TCC/keychain/app bundle behavior matters:
  ask for a macOS target environment.
- Browser profile or desktop app behavior matters:
  ask for a visible target app/session and use the native tools as appropriate —
  `browser:control-in-app-browser` / `chrome:control-chrome` for browser flows,
  `computer-use:computer-use` for desktop apps (see `cxc-dev-testing` §4.6).

## §4 Platform Matrix Scope

Matrix only platforms the project declares or the release claims to support.

| Claim | Minimum evidence |
|---|---|
| "Works on Linux" | Linux runner smoke |
| "Works on macOS" | macOS runner smoke; direct macOS proof if local UI/TCC/app behavior matters |
| "Works on Windows" | Windows runner smoke; direct Windows proof if PATH, shell, registry, or desktop behavior matters |
| "Cross-platform CLI" | Linux + macOS + Windows smoke unless support matrix is narrower |

## §5 Verification Handoff

Use `dev-testing/references/ci-pipeline.md` for runner matrix mechanics.
Use `computer-use:computer-use` only when direct visible app/OS proof is
needed (protocol: `cxc-dev-testing` §4.6). Do not duplicate desktop tool
instructions in this reference.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall