Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计提醒

deployment-automation部署自动化

Agent Skill

用于辅助云资源、部署、容器、基础设施和运维自动化任务。它适合让 Agent 检查配置、整理部署步骤、分析资源状态、生成排障思路或辅助云服务接入。使用时需要明确目标环境、账号权限、区域和资源组,区分本地测试与生产操作;涉及删除资源、重启服务、修改网络或权限配置时,应先确认影响范围。

总安装

8,049

周安装

239

GitHub Stars

12

下载量

1,828
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:deployment-automation(部署自动化)
来源仓库:https://github.com/happenings-community/requests-and-offers
仓库路径:skills/deployment-automation
安装命令:
npx skills add https://github.com/happenings-community/requests-and-offers --skill 'Deployment Automation'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/happenings-community/requests-and-offers --skill 'Deployment Automation'

简介

deployment-automation 用于辅助云资源、部署和容器运维自动化任务,适合检查配置和整理部署步骤。

  • 适用于分析资源状态、生成排障思路或辅助云服务接入的场景,帮助 Agent 管理基础设施。
  • 使用时需明确目标环境、账号权限和资源组,区分本地测试与生产操作。
  • 通过 GitHub 安装,支持 Codex、Claude、Cursor 和 Gemini CLI。
  • 涉及删除资源或修改网络配置时,应先确认影响范围,避免误操作。

SKILL.md

Deployment Automation Skill

Complete deployment system for Holochain hApps with proven patterns from successful production releases (v0.1.9, 100% cross-platform success).

Capabilities

  • Multi-Repository Coordination: Main repo (WebHapp), Kangaroo submodule (desktop apps), Homebrew (macOS distribution), git submodule sync
  • Cross-Platform Deployment: macOS ARM64 + x64, Windows x64, Linux DEB + AppImage, WebApp packaging, Holostrap production network
  • CI/CD Pipeline: GitHub Actions workflows, manual GitHub CLI asset uploads (100% reliable), cross-platform build verification
  • Release Automation: 7-step manual process (proven 100% success), version sync across repos, changelog and release notes

Quick Start

New Release

"Deploy version 0.2.0 with all platforms"

Deployment Troubleshooting

"The macOS build failed to upload assets"

Environment Setup

"Set up deployment environment for a new team member"

Proven Patterns

CI/CD Asset Upload Fix

This pattern eliminated asset upload failures in v0.1.9:

# Instead of unreliable electron-builder auto-publishing
- name: build and upload the app (macOS)
  run: |
    yarn build:mac-arm64
    ls dist
    # Use wildcard to handle filename variations
    find dist -name "*.dmg" -exec gh release upload "v${{ env.APP_VERSION }}" {} \;

7-Step Release Process

  1. Main Repository Updates - Version bump + changelog
  2. WebHapp Build - bun package in Nix environment
  3. GitHub Release Creation - Manual release with webhapp upload
  4. Kangaroo Repository Update - Copy webhapp + version sync
  5. CI/CD Trigger - Push to release branch
  6. Build Monitoring - Cross-platform build verification
  7. Release Notes Finalization - Cross-link desktop app links

Cross-Platform Build Benchmarks (v0.1.9)

  • macOS ARM64: 1m46s (fastest)
  • macOS x64: 3m2s
  • Windows x64: 2m54s
  • Linux x64: ~4m (includes post-install scripts)

Architecture Integration

Repository Structure

Main Repository (requests-and-offers)
├── WebHapp build and packaging
├── Release coordination and version management
└── Cross-repository linking

Kangaroo Submodule (deployment/kangaroo-electron)
├── Desktop app builds (Windows/macOS/Linux)
├── GitHub Actions CI/CD + code signing
└── Asset upload automation

Homebrew Repository (deployment/homebrew)
├── Formula management + checksum updates
└── macOS distribution

Deployment Flow

1. Pre-flight Validation    → Environment checks, auth verification
2. Version Synchronization  → All repositories aligned
3. WebHapp Build            → Production-ready bundle
4. Release Creation         → GitHub release with webhapp
5. Kangaroo Update          → Copy webhapp, trigger CI/CD
6. Multi-Platform Builds    → Parallel builds across platforms
7. Asset Verification       → All binaries uploaded successfully
8. Cross-Repository Updates → Homebrew formula, documentation
9. Post-Release Validation  → Downloads tested, links verified

Templates and Automation

  • GitHub Workflows: Optimized CI/CD pipeline templates
  • Kangaroo Config: Production-ready desktop app configuration
  • Deployment Config: Multi-environment configuration management
  • Release Notes: Structured documentation templates
  • Pre-flight Checks: Environment validation and prerequisites
  • Rollback Procedures: Emergency recovery automation

Troubleshooting

  • Asset Upload Failures: Builds complete but assets missing in release. Cause: electron-builder auto-publishing fails for branch builds. Fix: manual GitHub CLI uploads with wildcard patterns.
  • Build Failures: Verify webhapp exists in pouch directory, check version sync across repos, ensure Nix environment, validate GitHub CLI auth.
  • Repository Sync Issues: Submodules out of sync or version mismatches. Fix: proper git branch management and submodule updates.
  • macOS: Code signing certificate management
  • Windows: EV certificate configuration
  • Linux: Post-install script permissions
  • Recovery: Emergency rollback, partial release recovery, asset re-upload, repository resynchronization

Performance Metrics (v0.1.9)

  • Platform Success Rate: 100% (5/5 platforms)
  • Total Release Time: ~2.5 hours (including issue resolution)
  • Build Retry Count: 1 retry (macOS upload fix)
  • Asset Upload Success: 100% after manual pattern implementation

Best Practices

Release Management

  1. Follow the 7-step process exactly
  2. Use manual upload strategy over auto-publishing
  3. Use wildcard file discovery to eliminate filename mismatch failures
  4. Ensure cross-repository synchronization before starting

Build Optimization

  1. Run all platform builds concurrently
  2. Validate all uploads before proceeding
  3. Use Nix for consistent build environments
  4. Separate dev/test/prod configurations

Error Prevention

  1. Run pre-flight validation before every release
  2. Automate version synchronization
  3. Have rollback procedures ready
  4. Maintain comprehensive release notes

Knowledge Preservation

This skill preserves critical deployment knowledge:

  • Proven Patterns: Battle-tested from production releases
  • Troubleshooting: Solutions to common deployment issues
  • Best Practices: Evolution of deployment processes
  • Performance Benchmarks: Real-world metrics
  • Recovery Procedures: Emergency response patterns

Production-ready deployment infrastructure with proven reliability from successful Holochain application releases.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

Claude Code

26.41%
按下载量换算483

windsurf

26.39%
按下载量换算482

trae

20.61%
按下载量换算377

OpenCode

13.34%
按下载量换算244

Codex

8.4%
按下载量换算154

Antigravity

3.75%
按下载量换算69

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。来源字段存在多来源差异,先按来源优先级自动处理,无法消解时进入异常复核队列。

来源信息

继续浏览同类 Skills