「ops」の検索結果

Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs.

日本語の概要は準備中です。原文の説明を表示しています。

Azure DevOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure DevOps data.

日本語の概要は準備中です。原文の説明を表示しています。

Use when adding, removing, or updating a local organizer on a devopsdays event team - covers the team_members entry, the photo, and the mandatory email to info@devopsdays.org that gates the merge.

日本語の概要は準備中です。原文の説明を表示しています。

Argo CD for GitOps continuous delivery on Kubernetes. Use when the user needs to define applications declaratively, sync Kubernetes manifests from Git repositories, manage sync policies, and implement progressive delivery workflows.

日本語の概要は準備中です。原文の説明を表示しています。

软件架构 (含 应用架构 / 系统架构 / 分布式 后端架构 / 前后端 数据流 与 数据模型 设计 / API 边界 / 可扩展性 / 演进式架构 — 不含 硬件架构 / 纯企业架构 / 纯 DevOps / 纯安全架构) (software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).) Master OS — automated mastery of software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「软件架构」「系统设计」「system design」「应用架构」「service design」

日本語の概要は準備中です。原文の説明を表示しています。

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

Provides FinOps practices for cloud cost optimization, budget management, and resource rightsizing. Use when analyzing cloud spend, optimizing costs, or when user mentions 'finops', 'cloud cost', 'rightsizing', 'budget', 'cost allocation', 'reserved instance', 'spot instance', 'showback', 'chargeback'.

日本語の概要は準備中です。原文の説明を表示しています。

用户咨询腾讯云产品资源、AWS、阿里云等多云资源时，查看智能顾问架构图、架构目录、架构详情、架构评估结果、绘制架构图、开通智能顾问时、AI智能巡检、AI容量监测、AI混沌演练、AI云诊断、主动预警、架构健康度、云运维问答、云资源查询、云成本优化、安全合规、云资源盘点、闲置资源检查、云产品最佳实践等AIOps、ChatOps、CloudOps操作时使用。

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when users want to build, edit, or design pages and layouts on Divi 5 WordPress sites. Triggers include creating landing pages, hero sections, testimonial cards, pricing tables, feature grids, blog listing pages with post loops and pagination; adding or modifying sections on existing pages by page ID; setting up design systems with tokens and presets; theme builder templates for headers, footers, and post/page body layouts; mega menus and site navigation; saving to or loading from the Divi library; auditing or cleaning up presets. Handles animations, hover effects, responsive design, and dynamic content. Also covers special effects like WebGL shader backgrounds and advanced CSS animations via the DiviOps Design Library plugin. Do NOT use for custom PHP/plugins, child theme development, standalone CSS authoring, SQL queries, WooCommerce configuration, SEO setup, standalone Three.js projects without WordPress, or non-Divi builders like Elementor.

日本語の概要は準備中です。原文の説明を表示しています。

DiviOps harness primer — error envelope, capability handshake, dry-run plan shape, idempotency contract. Used as a shared primer by DiviOps target-coverage skills.

日本語の概要は準備中です。原文の説明を表示しています。

Encrypt .env files using SOPS + age. Converts dotenv to YAML format (avoids SOPS bug #1435), then encrypts. Auto-detects unencrypted .env files. Use when user mentions "encrypt env", "sops encrypt", "encrypt secrets", "encrypt .env", "encrypt environment", "re-encrypt", "update encrypted".

日本語の概要は準備中です。原文の説明を表示しています。

Add a new machine's age public key to .sops.yaml and re-encrypt all files. Use for multi-machine setups. Use when user mentions "add key", "add machine", "sops add key", "new machine", "authorize machine", "share key", "add public key", "multi machine sops".

日本語の概要は準備中です。原文の説明を表示しています。

Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.

日本語の概要は準備中です。原文の説明を表示しています。

DeepSeek V4.x Flash を複数 provider（OpenCode Go / NVIDIA Build / DeepInfra）経由で動かすときの失敗型・切り分け・運用の正本。DSML tool-call drift の検出と salvage、quota 層の確認、provider 選定に使う。「DeepSeek が応答しない」「tool call が空」「429 が続く」といった症状で使う。ユーザーが /deepseek-ops と入力したら使う。

データ準備からモデル学習、検証、本番デプロイメントまでのエンドツーエンドMLOpsパイプラインを構築します。MLパイプラインの作成、MLOpsプラクティスの実装、またはモデル学習とデプロイメントワークフローの自動化時に使用します。

Use when working with Allure Testops — allure TestOps test management and analytics platform monitoring. Covers project dashboards, launch tracking, test case management, defect clustering, environment matrix analysis, and CI/CD integration review. Use when managing test cases in Allure TestOps, reviewing launch results, analyzing flaky tests, or tracking quality trends.

日本語の概要は準備中です。原文の説明を表示しています。

DevOps & Infrastructure IA — Gère le VPS, Docker, déploiements, monitoring, sécurité, tunnels Cloudflare. Expert Hetzner + Coolify + self-hosting.

日本語の概要は準備中です。原文の説明を表示しています。

DevOps infra v2 — VPS, Docker, Coolify, CI/CD, monitoring, Tailscale

日本語の概要は準備中です。原文の説明を表示しています。

DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.

日本語の概要は準備中です。原文の説明を表示しています。

用户咨询腾讯云产品资源、AWS、阿里云等多云资源时，查看智能顾问架构图、架构目录、架构详情、架构评估结果、绘制架构图、开通智能顾问时、AI智能巡检、AI容量监测、AI混沌演练、AI云诊断、主动预警、架构健康度、云运维问答、云资源查询、云成本优化、安全合规、云资源盘点、闲置资源检查、云产品最佳实践等AIOps、ChatOps、CloudOps操作时使用。

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret Tespit.

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.

日本語の概要は準備中です。原文の説明を表示しています。

Blender Python API リファレンス。bpy / bmesh / mathutils / gpu / bpy_extras モジュール、 bpy.data / bpy.context / bpy.ops / bpy.types / bpy.props コア API。 Mesh / Modifier / Geometry Nodes / Armature / Keyframe / Driver / Shape Key / NLA、 Cycles / EEVEE / Shader Nodes / Rigid Body / Cloth / Fluid / Compositor Nodes / AOV、 headless CLI レンダリング、add-on 開発、Extensions システム、MCP Server (Model Context Protocol)。