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

operate-devops

Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.

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

연동 도구Kubernetes
설치 방법 보기

포함된 파일(3)

  • SKILL.md2.4 KB
  • agents/openai.yaml214 B
  • references/change-safety.md2.4 KB

SKILL.md(원문)

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

Operate DevOps

Workflow

  1. Read repository and environment guidance before changing configuration.
  2. Identify the target environment, current state, owning tool, blast radius, and approval boundary.
  3. Separate diagnosis, proposed change, apply, verification, and rollback.
  4. Prefer a dry run, plan, diff, render, lint, or local build before any apply step.
  5. Make the smallest reversible change.
  6. Validate configuration syntax and policy.
  7. Test failure behavior and rollback in the safest available environment.
  8. Review the diff for secrets, broad permissions, unpinned behavior, and unintended targets.

Guardrails

  • Confirm account, cluster, subscription, region, namespace, and environment before state-changing commands.
  • Keep credentials out of code, command output, and generated artifacts.
  • Use least-privilege identities and scoped approvals.
  • Do not silently apply infrastructure because a plan succeeded.
  • Do not delete, force-replace, rotate, deploy, or migrate live resources without explicit authorization.
  • Preserve a recovery path for availability, routing, storage, and identity changes.
  • Do not weaken security controls merely to make automation pass.
  • Treat third-party actions, base images, and pipeline dependencies as supply-chain inputs.

Change safety

Read references/change-safety.md for deployment, infrastructure, CI, secret, permission, or data-path changes.

Verification

Use repository-native commands in this order:

format/lint → validate/render → plan/diff → policy tests → staged rollout check

Report exactly which environment was inspected and which commands were not run.

Acceptance criteria

  • Target and blast radius are explicit.
  • A preview or equivalent validation was inspected.
  • Credentials and permissions follow least privilege.
  • Rollback or roll-forward steps are concrete.
  • Monitoring proves success and detects regression.
  • The final report separates proposed, executed, and unverified actions.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

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

Phelan164/codex-howto142026년 10월 17일 업데이트

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

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

Phelan164/codex-howto142026년 10월 17일 업데이트

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

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

Phelan164/codex-howto142026년 10월 17일 업데이트

Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.

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

Phelan164/codex-howto142026년 10월 17일 업데이트

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

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

Phelan164/codex-howto142026년 10월 17일 업데이트

Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.

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

Phelan164/codex-howto142026년 10월 17일 업데이트

Phelan164의 스킬 모두 보기

이 스킬의 문제 신고