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/delivery-boundaries.md

View on GitHub
## §6 Cross-References

| Topic | Canonical Owner | What dev-devops defers |
|-------|----------------|----------------------|
| Test strategy & CI test stages | [dev-testing CI stages](../../dev-testing/references/ci-integration.md) | Test pyramid, coverage gates |
| Backend observability code patterns | `dev-backend` `observability.md` | OTel SDK setup, structured logging |
| Security hardening (app-layer) | `dev-security` | OWASP, auth, input validation |
| SBOM/signing depth | [dev-security SBOM](../../dev-security/references/supply-chain-sbom.md) | Supply-chain evidence policy beyond image scan gates |
| Architecture module boundaries | `dev-architecture` | Coupling taxonomy, barrel discipline |
| Scaffolding conventions | `dev-scaffolding` | File naming, project structure |
| Frontend build/bundle | `dev-frontend` | Vite/webpack config, SSR |

**dev-devops owns**: container builds, deploy pipelines, K8s manifests, IaC modules, SRE/incident response, edge infra, ML infra. DevOps owns operational scan execution and release gates; `dev-security` owns security policy, severity thresholds, and required evidence.
**dev-backend owns**: application-layer observability code, API design, health check implementation.
Overlap: observability alerting rules (dev-devops §5) ↔ observability code instrumentation (dev-backend `observability.md`). Cross-ref both.

## Reference Reading Order

Read `package-release.md` for package publishing, registry auth, npm/PyPI
trusted publishing, Bun-to-npm release decisions, and downstream package
channels. Read `cross-platform-release.md` when a release claim depends on
OS-local behavior that CI may not prove. Read `homebrew.md` for Formula/Cask
distribution work. Read `platform-engineering.md` for broader DevOps capability
refresh, DORA, provider routing, and platform guardrails. Read `docker.md` + `ci-cd-deploy.md` first for containerized deploy workflows.
For K8s-specific work, add `kubernetes.md`. For SRE/on-call, add `sre-foundations.md`.

## Routing Role

Build reliable, secure, and automated infrastructure and delivery pipelines.
This skill is a routing role that activates by **change-surface**: whenever the work primarily touches containers, CI/CD, deployment, cloud/runtime infrastructure, Kubernetes, IaC, release engineering, or SRE operations, use this skill and then load the relevant references.
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: 197kUpdated 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