开发敏感数据github未标认证来源可访问许可证需确认审计通过

building-gitops-workflows（构建 gitops 工作流程）

Agent Skill

building-gitops-workflows 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

582

周安装

GitHub Stars

2,102

下载量

204

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：building-gitops-workflows（构建 gitops 工作流程）
来源仓库：https://github.com/jeremylongshore/claude-code-plugins-plus-skills
仓库路径：skills/building-gitops-workflows
安装命令：
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill building-gitops-workflows
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill building-gitops-workflows

简介

用于基于 ArgoCD 或 Flux 构建 GitOps 交付流水线，实现 Kubernetes 应用的声明式管理。

适用于多环境部署、同步策略配置与 RBAC 权限控制等持续交付场景。
支持 Helm Chart 安装与通知集成，提供完整的 CI/CD 与运维自动化解决方案。
安装使用 GitHub 仓库，需提前准备可访问的 K8s 集群与镜像仓库权限。
building-gitops-workflows 属于开发类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Building GitOps Workflows

Overview

Construct GitOps workflows using ArgoCD or Flux to implement declarative, Git-driven continuous delivery for Kubernetes. Generate Application/Kustomization manifests, configure sync policies, set up multi-environment promotion, and implement RBAC and notification integrations.

Prerequisites

Kubernetes cluster accessible via kubectl with admin permissions
Git repository for storing Kubernetes manifests (separate from application code recommended)
ArgoCD or Flux installed on the cluster, or Helm charts ready for installation
Container images built and pushed to a registry accessible from the cluster
SSH key or access token for Git repository authentication from the cluster

Instructions

Choose the GitOps tool based on requirements: ArgoCD for UI-driven management, Flux for lightweight Git-native approach
Design the repository structure: environments/{dev,staging,prod}/ with Kustomize overlays or Helm values per environment
Generate ArgoCD Application or Flux Kustomization manifests pointing to the Git repository path for each environment
Configure sync policy: enable automated.selfHeal and automated.prune for non-production; use manual sync for production
Set up Git repository credentials as a Kubernetes Secret for the GitOps operator
Implement environment promotion: update the image tag in staging manifests, test, then promote to production via PR
Configure notifications: Slack/email alerts on sync success, failure, or health degradation via ArgoCD Notifications or Flux Alert Provider
Add RBAC: restrict who can sync production applications and who can modify GitOps configurations
Validate the setup: push a manifest change to Git and verify the GitOps operator detects and applies it within the sync interval

Output

ArgoCD Application or Flux Kustomization manifests per environment
Git repository structure with Kustomize bases and overlays
RBAC configuration (ArgoCD AppProject, Kubernetes RBAC)
Notification configuration (Slack webhooks, email)
CI pipeline step to update image tags in the GitOps repository after build

Error Handling

Error	Cause	Solution
`ComparisonError: Failed to load target state`	Invalid manifest path or Git ref	Verify `path:` and `targetRevision:` in the Application manifest; check repo structure
`Authentication failed for repository`	SSH key or token not configured or expired	Create/update the Git credentials Secret; verify deploy key has read access
`Application is OutOfSync but not syncing`	Automated sync disabled or sync window closed	Enable `automated:` in syncPolicy or trigger manual sync with `argocd app sync`
`Resource already exists and is not managed`	Resource created outside of GitOps	Add the `argocd.argoproj.io/managed-by` annotation or delete the conflicting resource
`Sync failed: health check timeout`	Application pods not becoming ready after sync	Check pod logs; verify resource requests fit node capacity; increase health check timeout

Examples

"Set up ArgoCD with three Application manifests for dev, staging, and production, each pointing to a different Kustomize overlay in the GitOps repo."
"Configure Flux with automatic image updates: scan ECR for new tags matching v*, update the staging manifests, and create a PR for production promotion."
"Create an ArgoCD AppProject that restricts the production application to specific namespaces and requires manual sync with admin-only access."

Resources

ArgoCD documentation: https://argo-cd.readthedocs.io/en/stable/
Flux documentation: https://fluxcd.io/flux/
GitOps principles: https://opengitops.dev/
Kustomize: https://kustomize.io/

适合场景

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.18%

按下载量换算74

Claude

32.23%

按下载量换算66

Cursor

17%

按下载量换算35

Gemini CLI

9.62%

按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置，应进入高风险复核队列，默认不自动发布。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/jeremylongshore/claude-code-plugins-plus-skills

SKILL.md 来源

github.com

/jeremylongshore/claude-code-plugins-plus-skills/tree/main/skills/building-gitops-workflows

skills-sh

skills.sh

/jeremylongshore/claude-code-plugins-plus-skills/building-gitops-workflows

继续浏览同类 Skills

更多开发 Skills（21,746）返回 Skills 目录

上一个 Skill

building-github-index（building GitHub index 开发）

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项，并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作；涉及创建 PR、修改 Issue、推送分支或访问私有仓库时，应确认 token 权限、目标仓库范围和用户授权。

下一个 Skill

building-graphql-server（building GraphQL server 文档）

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则；涉及生成接口文档时，应避免凭空补字段，最好从现有代码、schema 或接口样例中提取事实。