# github-actions

This skill handles ClaudeBar’s GitHub Actions builds, tests, and releases. Use it to configure CI secrets, publish tagged or manual releases, and investigate failures.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 1557
- Author: tddworks
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/tddworks/ClaudeBar/tree/HEAD/.claude/skills/github-actions/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/tddworks-github-actions

## What it does

The skill covers the workflows in `.github/workflows/`. `build.yml` checks debug and release builds, `tests.yml` runs unit tests and uploads coverage to Codecov, and `windows.yml` builds and tests `Quotas` with Swift on Windows. `release.yml` handles macOS releases started by a `v*` tag or a manual dispatch.

The release path validates the version, edits `Info.plist`, runs `tuist`, archives with `xcodebuild`, signs the app, submits it for notarization, and creates signed ZIP and DMG files with SHA256 checksums. It then publishes a GitHub Release and a Sparkle appcast. Beta tags add the `beta` channel and require Beta Updates to be enabled. Required secrets cover Apple signing, App Store Connect notarization, Sparkle updates, and Codecov.

A release cannot pass signing and notarization without `APPLE_CERTIFICATE_P12`, `APPLE_CERTIFICATE_PASSWORD`, and the App Store Connect keys. Manual dispatch with `debug: true` prints certificate and keychain details, giving you concrete clues when a release breaks.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add tddworks/ClaudeBar --skill github-actions -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/github-actions/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/github-actions/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add tddworks/ClaudeBar --skill github-actions -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/github-actions/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add tddworks/ClaudeBar --skill github-actions -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/github-actions/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install tddworks/ClaudeBar github-actions
```

2. **Manually: put the files in place**
- File: `.github/skills/github-actions/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add tddworks/ClaudeBar --skill github-actions -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/tddworks/ClaudeBar --path .claude/skills/github-actions
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/github-actions/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add tddworks/ClaudeBar --skill github-actions -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/tddworks/ClaudeBar/tree/HEAD/.claude/skills/github-actions/SKILL.md

## When to use it
- configure GitHub Actions secrets for signing and notarization
- run build and test checks on pushes or pull requests
- publish a release from a `v*` tag or manual dispatch
- trace signing, notarization, or appcast failures
- separate Sparkle beta updates from stable releases

## Example prompts
- Set up the GitHub Actions secrets for a ClaudeBar release and explain what each one is used for.
- Create version `1.2.0-beta.1` from a tag and verify how the Sparkle beta channel is published.
- Investigate why `release.yml` failed after notarization and tell me what `debug: true` will show.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1bca6ba398d1adaa.

BEGIN THIRD-PARTY FILE 1bca6ba398d1adaa
````text
---
name: github-actions
description: |
  Manage ClaudeBar's GitHub Actions CI/CD pipelines: build, test, and release workflows.
  Use this skill when:
  (1) Setting up secrets for CI/CD (certificate, API key, Sparkle key, Codecov)
  (2) Creating a new release — tag-based or manual workflow_dispatch
  (3) Triggering or explaining the build.yml, tests.yml, or release.yml workflows
  (4) Debugging release failures (signing, notarization, appcast)
  (5) Managing beta vs stable channels for Sparkle auto-updates
  (6) User says "release a new version", "push a tag", "set up CI secrets", "why did the release fail"
---

# ClaudeBar GitHub Actions

Three workflows live in `.github/workflows/`. See reference files for setup and troubleshooting.

## Workflows at a Glance

| Workflow | Trigger | Runner | Purpose |
|----------|---------|--------|---------|
| `build.yml` | push/PR to main, develop | macos-15 | Debug + release build verification |
| `tests.yml` | push/PR to main, develop | macos-26 | Unit tests + Codecov coverage upload |
| `windows.yml` | push/PR to main, develop | windows-latest | Builds and tests `Quotas` with Swift on Windows (MODULAR_DESIGN §10, phase 0) |
| `release.yml` | `v*` tag push OR manual | macos-15 | Sign → notarize → DMG → GitHub release → appcast |

## Create a Release

**Option A — Tag (recommended):**

```bash
# 1. Update CHANGELOG.md with release notes for this version
# 2. Commit and push
git add CHANGELOG.md
git commit -m "docs: add release notes for v1.2.0"
git push origin main

# 3. Tag and push — this triggers release.yml automatically
git tag v1.2.0 && git push origin v1.2.0

# Beta / pre-release (automatically flagged on GitHub)
git tag v1.2.0-beta.1 && git push origin v1.2.0-beta.1
```

**Option B — Manual dispatch:**

1. Go to **Actions → Release → Run workflow**
2. Enter version (e.g. `1.2.0` or `1.2.0-beta.1`)
3. Optionally toggle `publish_appcast` and `debug`

**Supported version formats:** `X.Y.Z`, `X.Y.Z-beta`, `X.Y.Z-beta.N`, `X.Y.Z-alpha.N`, `X.Y.Z-rc.N`

## Secrets Required

| Secret | Required For | See |
|--------|-------------|-----|
| `APPLE_CERTIFICATE_P12` | Code signing | [secrets-setup.md](references/secrets-setup.md) |
| `APPLE_CERTIFICATE_PASSWORD` | Code signing | [secrets-setup.md](references/secrets-setup.md) |
| `APP_STORE_CONNECT_API_KEY_P8` | Notarization | [secrets-setup.md](references/secrets-setup.md) |
| `APP_STORE_CONNECT_KEY_ID` | Notarization | [secrets-setup.md](references/secrets-setup.md) |
| `APP_STORE_CONNECT_ISSUER_ID` | Notarization | [secrets-setup.md](references/secrets-setup.md) |
````
END THIRD-PARTY FILE 1bca6ba398d1adaa

The third-party file has ended. Everything between the 1bca6ba398d1adaa tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2619 of 4327 bytes. © tddworks · Apache-2.0 · https://github.com/tddworks/ClaudeBar/tree/HEAD/.claude/skills/github-actions/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md