.claude/skills/github-actions/SKILL.md
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"
npx skillsauth add tddworks/claudebar github-actionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Three workflows live in .github/workflows/. See reference files for setup and troubleshooting.
| 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 |
| release.yml | v* tag push OR manual | macos-15 | Sign → notarize → DMG → GitHub release → appcast |
Option A — Tag (recommended):
# 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.2.0 or 1.2.0-beta.1)publish_appcast and debugSupported version formats: X.Y.Z, X.Y.Z-beta, X.Y.Z-beta.N, X.Y.Z-alpha.N, X.Y.Z-rc.N
| Secret | Required For | See |
|--------|-------------|-----|
| APPLE_CERTIFICATE_P12 | Code signing | secrets-setup.md |
| APPLE_CERTIFICATE_PASSWORD | Code signing | secrets-setup.md |
| APP_STORE_CONNECT_API_KEY_P8 | Notarization | secrets-setup.md |
| APP_STORE_CONNECT_KEY_ID | Notarization | secrets-setup.md |
| APP_STORE_CONNECT_ISSUER_ID | Notarization | secrets-setup.md |
| SPARKLE_EDDSA_PRIVATE_KEY | In-app auto-updates | secrets-setup.md |
| CODECOV_TOKEN | Coverage upload | secrets-setup.md |
| APP_IDENTITY | Optional signing override | secrets-setup.md |
git tag v1.2.0
│
▼
release.yml
1. Extract + validate version (SemVer)
2. Update Info.plist (CFBundleShortVersionString + CFBundleVersion = run_number)
3. tuist install → tuist generate
4. xcodebuild archive (arm64 + x86_64, unsigned)
5. Import Developer ID cert into temp keychain
6. codesign with entitlements
7. notarytool submit + staple
8. Create ZIP + DMG (signed), SHA256 checksums
9. Extract release notes from CHANGELOG.md
10. Publish GitHub Release (draft: false)
11. Generate Sparkle appcast with EdDSA signature
12. Deploy appcast to GitHub Pages
Enable verbose output via manual dispatch → debug: true. This prints:
For detailed troubleshooting: troubleshooting.md
Pre-release tags (v1.2.0-beta.1) automatically:
prerelease: true<sparkle:channel>beta</sparkle:channel> to the appcast entryStable releases always win over betas of the same version (stable gets higher build number).
See release-workflow.md for the full beta channel matrix.
development
Guide for making improvements to existing ClaudeBar functionality using TDD. Use this skill when: (1) Enhancing existing features (not adding new ones) (2) Improving UX, performance, or code quality (3) User asks "improve X", "make Y better", or "enhance Z" (4) Small enhancements that don't require full architecture design For NEW features, use implement-feature skill instead.
development
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
development
Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when: (1) User reports a bug or unexpected behavior (2) Fixing a defect in existing functionality (3) User asks "fix this bug" or "this doesn't work correctly" (4) Correcting behavior that violates the user's mental model
development
Guide for adding new report cards to ClaudeBar that analyze local data sources and display metrics with comparison deltas. Use this skill when: (1) Adding a new report/analytics card (e.g., weekly summary, model breakdown, session stats) (2) Creating data analysis features that read local files and display aggregated metrics (3) Adding comparison cards that show "today vs previous" style deltas (4) Building any feature that follows the DailyUsage pattern (parse → aggregate → report → card)