원클릭으로 Manus에서 모든 스킬 실행

$pwd:

github-actions

Name: Github Actions
Author: tddworks

// 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"

Manus에서 실행

$ git log --oneline --stat

stars:1,189

forks:98

updated:2026년 2월 25일 05:46

파일 탐색기

3 개 파일

SKILL.md

readonly

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
`release.yml`	`v*` tag push OR manual	macos-15	Sign → notarize → DMG → GitHub release → appcast

Create a Release

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:

Go to Actions → Release → Run workflow
Enter version (e.g. 1.2.0 or 1.2.0-beta.1)
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
`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

What the Release Pipeline Does

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

Debugging Failures

Enable verbose output via manual dispatch → debug: true. This prints:

P12 certificate details and contents
All identities in the signing keychain
Certificate subject and expiry dates

For detailed troubleshooting: troubleshooting.md

Beta Channel

Pre-release tags (v1.2.0-beta.1) automatically:

Set GitHub release as prerelease: true
Add <sparkle:channel>beta</sparkle:channel> to the appcast entry
Are only offered to users with Beta Updates enabled in Settings

Stable releases always win over betas of the same version (stable gets higher build number).

See release-workflow.md for the full beta channel matrix.

related-skills.json

같은 저장소

add-provider.md

from "tddworks/ClaudeBar"

Guide for adding new AI providers to ClaudeBar using TDD patterns. Use this skill when: (1) Adding a new AI assistant provider (like Antigravity, Cursor, etc.) (2) Creating a usage probe for a CLI tool or local API (3) Following TDD to implement provider integration (4) User asks "how do I add a new provider" or "create a provider for X"

2026-03-121.2k

add-report.md

from "tddworks/ClaudeBar"

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)

2026-03-111.2k

implement-feature.md

from "tddworks/ClaudeBar"

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

2026-01-051.2k

fix-bug.md

from "tddworks/ClaudeBar"

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

2026-01-021.2k

improvement.md

from "tddworks/ClaudeBar"

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.

2026-01-021.2k

package.json

"author": "tddworks"

"repository": "tddworks/ClaudeBar"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

네트워크·컴퓨터 시스템 관리자컴퓨터 및 수학직15-1244L4

name

github-actions

description

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
`release.yml`	`v*` tag push OR manual	macos-15	Sign → notarize → DMG → GitHub release → appcast

Create a Release

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:

Go to Actions → Release → Run workflow
Enter version (e.g. 1.2.0 or 1.2.0-beta.1)
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
`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

What the Release Pipeline Does

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

Debugging Failures

Enable verbose output via manual dispatch → debug: true. This prints:

P12 certificate details and contents
All identities in the signing keychain
Certificate subject and expiry dates

For detailed troubleshooting: troubleshooting.md

Beta Channel

Pre-release tags (v1.2.0-beta.1) automatically:

Set GitHub release as prerelease: true
Add <sparkle:channel>beta</sparkle:channel> to the appcast entry
Are only offered to users with Beta Updates enabled in Settings

Stable releases always win over betas of the same version (stable gets higher build number).

See release-workflow.md for the full beta channel matrix.

github-actions

ClaudeBar GitHub Actions

Workflows at a Glance

Create a Release

Secrets Required

What the Release Pipeline Does

Debugging Failures

Beta Channel

이 저장소의 다른 Skills

ClaudeBar GitHub Actions

Workflows at a Glance

Create a Release

Secrets Required

What the Release Pipeline Does

Debugging Failures

Beta Channel

이 저장소의 다른 Skills