7천건 · 관련도순
Manage Azure DevOps projects, repositories, pull requests, pipelines, and work items through command-line tools. The skill guides authentication, resource operations, and automation scripts, with references for builds, permissions, packages, and common errors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up and troubleshoot automated build, test, and deployment workflows in KubeSphere DevOps. Covers Jenkins integration, project management, multi-cluster installation, and ArgoCD integration for deployments managed through Git.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage credentials for Git access and deployments in KubeSphere DevOps. Covers SSH keys, passwords, API tokens, and Kubernetes connection settings, including their use in Jenkins pipelines and troubleshooting synchronization failures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and run KubeSphere DevOps pipelines connected to Jenkins to automate builds and tests. Covers branch-specific workflows, required input parameters, private repository credentials, execution monitoring, logs, and downloading build output files.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Configure and troubleshoot Jenkins in KubeSphere DevOps, including login integration and build agents, the environments that run pipeline tasks. Get guidance for starting builds through the API, checking logs and status, and downloading build artifacts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Configure ArgoCD in KubeSphere DevOps for GitOps, which keeps deployed applications aligned with configuration stored in Git. Covers application management, repository credentials, shared sign-in, multiple clusters, and troubleshooting synchronization problems.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when you need Azure DevOps CLI guidance to verify installation, configure organization and project context, discover work item IDs by optional WIQL filters, and execute safe work-item create/update operations. Uses an interactive install gate - if `az` or the Azure DevOps extension is missing, ask whether to show installation guidance before any work item commands. This should trigger for requests such as Azure DevOps work item list; List Azure Boards work item IDs; Azure DevOps WIQL query; Azure DevOps CLI planning workflow. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search software, data, and engineering jobs across countries through freehire.me. Filter by skills, seniority, location, posting age, and remote work, and retrieve full descriptions to assess opportunities or inspect a specific posting.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Operate KubeSphere DevOps pipelines within a permitted project using KubeSphere APIs and OAuth authentication. Create pipelines, run selected branches, monitor execution, and retrieve logs or build artifacts without requiring cluster administrator access or direct Jenkins access.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up Azure Pipelines for CI/CD, configure build and release pipelines, manage Azure DevOps projects, and integrate with Azure services. Use when working with Azure DevOps Services or Server for enterprise DevOps workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an admin or partner needs to package an Experience Cloud (Community) site as a reusable Lightning Bolt Solution for distribution — covers the export workflow from Experience Builder, what gets bundled (ExperienceBundle, custom apps, flow categories, theme, layouts, navigation menus) versus what does NOT (data, CMS content, files), choosing Bolt vs managed package vs unlocked package vs cloning a site, sandbox-to-production promotion, multi-org distribution, AppExchange listing as a Bolt, and template versioning via the LightningBolt metadata `versionNumber`. Triggers: 'turn this community into a reusable template', 'package an Experience Cloud site to ship to multiple orgs', 'export Experience Builder template for AppExchange', 'should we use a Bolt or a managed package for this community', 'create an industry-specific community starter', 'how do we version our partner portal template', 'distribute branded Experience site across business units'. NOT for general Experience Cloud site build, content, or member setup (use admin/experience-cloud-site-setup, admin/experience-cloud-cms-content, admin/experience-cloud-member-management). NOT for shipping Apex / LWC / data-model functionality as a product (use devops/managed-package-development, devops/second-generation-managed-packages, devops/unlocked-package-development). NOT for moving a single Experience site between sandbox and prod as a one-off (use devops/experience-cloud-deployment-admin, devops/cicd-for-experience-cloud).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when authoring, reviewing, or maintaining Salesforce DevOps operational documents — runbooks, environment matrices, deployment guides, and post-deploy validation checklists. Triggers: 'runbook', 'environment matrix', 'deployment guide', 'pre-deploy checklist', 'post-deploy validation', 'how do I document a deployment', 'rollback procedure template'. NOT for what actually belongs on the pre-deploy gate — use devops/pre-deployment-checklist. NOT for release calendar, versioning, or go/no-go governance — use devops/release-management. Also covers: the devops-process YAML artefact (environment ladder, change-request state machine, deploy contract, deploy order, RACI), the deployOptions the runbook must record (checkOnly, testLevel, rollbackOnError, ignoreWarnings, purgeOnDelete, singlePackage, runTests), destructiveChangesPre/Post ordering, and the change-request emergency path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive skill for working with Azure DevOps REST API across all services including Boards (work items, queries, backlogs), Repos (Git, pull requests, commits), Pipelines (builds, releases, deployments), Test Plans, Artifacts, organizations, projects, security, extensions, and more. Use when implementing Azure DevOps integrations, automating DevOps workflows, or building applications that interact with Azure DevOps services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Setup and diagnostics for the AWS DevOps Agent MCP connection. Triggers when aws-devops-agent is missing from .mcp.json, when the connection is broken, or when the user says "set up devops agent" / "configure agent". Does NOT trigger if the MCP is already connected and working.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge for Azure DevOps development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing org/projects, repos, pipelines, work items, dashboards/analytics, or Azure DevOps Server deployments, and other Azure DevOps related development tasks. Not for Azure Boards (use azure-boards), Azure Pipelines (use azure-pipelines), Azure Repos (use azure-repos), Azure Test Plans (use azure-test-plans).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
World-class DevOps engineering - cloud architecture, CI/CD pipelines, infrastructure as code, and the battle scars from keeping production running at 3amUse when "devops, infrastructure, deployment, ci/cd, docker, kubernetes, aws, gcp, azure, terraform, cloudflare, vercel, monitoring, alerting, pipeline, container, scaling, downtime, incident, sre, devops, infrastructure, cloud, ci-cd, monitoring, reliability, sre, containers" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when automating or scripting Azure DevOps from the command line with az devops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Azure Devops — azure DevOps comprehensive management. Covers pipelines, boards, repositories, artifacts, test plans, work item tracking, and release management. Use when checking pipeline status, managing work items, investigating build failures, or auditing Azure DevOps project configurations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Azure Devops Boards — azure DevOps Boards work item tracking, sprint analysis, burndown metrics, team velocity, and backlog management via Azure DevOps CLI extension.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve resumes for software engineering, technical product management, data, and DevOps roles. Organize technical skills, connect achievements to business results, and highlight projects in a format suited to applicant tracking systems, software used to process job applications, and recruiters.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan Azure infrastructure around application needs, scale, and budget. Generate Bicep templates, files that define cloud resources as code, then review estimated costs, configure deployment pipelines, and check security settings before production.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.