lidge-jun/codexclaw / plugins/codexclaw/skills/dev-devops
cxc-dev-devops
UnverifiedUse for infra, CI/CD, releases, repo policy, worktree cleanup and native desktop apps. Triggers: Dockerfile, K8s, IaC, SRE, Tauri, 스택 PR CI, 배포, 인프라, 쿠버네티스, 브랜치 정리, 브랜치 삭제, 워크트리 정리, 저장소 세팅, 브랜치 보호, 에이전트 PR, PR 정책, 데스크톱 앱, 메뉴 막대.
Dev-DevOps — Production Infrastructure & Delivery
Backend handoff rule: When a deploy/SRE gate needs app behavior,
dev-backendimplements the hook (health handler, readiness dependency check, trace/span/log fields, migration compatibility, shutdown hook).dev-devopsdefines the operational gate, rollout/rollback behavior, alert policy, and release proof. This skill owns deployment strategy, rollback proof, observability operations, health/readiness operational gates, SLOs, incident response, and infrastructure/runtime delivery.
Class, fast path, rule authority, proof, and safety: dev. Current/public evidence: dev routing.
Severity and rule authority are distinct (dev §0.2). Safety/correctness and release
proof remain mandatory; architecture/tool preferences need project-specific justification.
§2.7 Release Proof Contract (STRICT)
Rule (DEVOPS-RELEASE-PROOF-01): A release claim must name the artifact digest, workflow/builder identity, deploy target/environment, smoke-test evidence, and rollback evidence. Keep the proof at router level; detailed package, platform, and SLSA mechanics live in package-release.md, cross-platform-release.md, and platform-engineering.md.
Modular References
| Condition | Reference |
|---|---|
| Container builds or image push | container-build-rules.md; docker.md |
| Deploy pipeline, rollout, rollback, secrets, or GitOps | deployment-pipeline-rules.md; ci-cd-deploy.md |
| Freeze or GO/NO-GO publication decision | release-readiness.md |
| Package publishing, registry auth, trusted publishing, or distribution channels | package-release.md |
| Release depends on OS-local behavior | cross-platform-release.md |
| Tauri, AppKit/SwiftUI, WidgetKit, menu-bar/tray, embedded runtimes; desktop acceptance or release readiness | native-desktop-acceptance.md |
| TCC, Gatekeeper, login/background items, keychain, or Apple Events approval prompts | macos-system-approvals.md |
| Homebrew Formula/Cask distribution | homebrew.md |
| Platform, DORA, provider routing, or SLSA handoff | platform-engineering.md |
| K8s deploys, Gateway API, scaling, or manifest checks | kubernetes-basics.md; kubernetes.md |
| Stacked/dependent PRs or unexpected CI runs | Stacked PRs |
| Authorized branch/worktree cleanup | branch-hygiene-rules.md; branch-lifecycle.md |
| Repository setup, rulesets, auto-delete, or PR limits | repo-bootstrap.md |
| Agent-authored intake policy or superseded PRs | agent-pr-intake.md |
| Local worktree/branch GC or scheduled cleanup | local-gc.md |
| IaC modules, state, or blast radius | infrastructure-code-rules.md; iac.md |
| SLO, error budget, incident, or runbook | sre-basics.md; sre-foundations.md |
| Edge/serverless delivery | edge-serverless.md |
| GPU clusters, model registry, scaling, or MLOps | ml-infra.md |
| Ownership overlaps with app, testing, or security work | delivery-boundaries.md |
| Submitting infrastructure changes | infrastructure-preflight.md |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 117k | Updated | Claude CodeCodex | Unverified | Install |