本文へ移動
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.

インストール方法を見る

含まれるファイル(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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

Phelan164 のスキルをすべて見る

このスキルの問題を報告する