メニュー
Ship new Qaio version. Bump semver across all packages, tag, push, let CI build + sign + notarize. STOP at draft — user publishes manually. Defaults patch bump. Minor needs explicit user permission.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Build Qaio App locally (macOS). Clean stale artifacts, pnpm tauri build, notarize DMG manually (Tauri skips), staple, verify, copy to ~/Desktop/Qaio-{version}.dmg. Fallback when CI broken.
Debug bugs in Qaio. NEVER guess. Read log files first (backend + frontend). Add targeted tracing/logger if not enough info. Never ask user to copy-paste terminal output.
Process a batch of PDF or CSV bank and credit-card statements end to end: extract every transaction (parallel Haiku subagents), canonicalize the party names, categorize against your locked chart of accounts (parallel Sonnet subagents), detect inter-account transfers, and assemble a reviewed Google Sheets workbook with a formula-driven P&L. Reconciliation mismatches surface as warnings, low-confidence categorizations land in Suspense — I never invent an account code, never silently plug a number, never post to your accounting system.
Set up your books from scratch with one founder interview that captures entity, fiscal year, accounting method, registered accounts, payroll posture, revenue model, investor cadence, and tax preparer, then writes the live bookkeeping brief every other skill reads first. Sub-mode `mode=opening-balances` captures your opening trial balance from a spreadsheet, CSV, or prior-accountant export. I never connect a bank, post to a general ledger, or move money from this skill — facts and a brief, full stop.
Tell me the basics about your company so I can give you better legal help. I ask a few quick questions about your entity, cap table, contracts in force, templates, and any open risks. You only need to do this once, and I keep it updated as things change.
Tell me the basics about your company, your customer, and how you talk so I can give you better marketing help. I ask a few quick questions about your product, positioning, ideal customer, voice, and what you're selling right now. You only need to do this once, and I keep it updated as things change.
SOC 職業分類に基づく
| name | release |
| description | Ship new Qaio version. Bump semver across all packages, tag, push, let CI build + sign + notarize. STOP at draft — user publishes manually. Defaults patch bump. Minor needs explicit user permission. |
Version. Bump. Tag. Push. Done.
All packages share ONE version. Every release bumps ALL.
0.x.y0.3.0 → 0.3.1). Do this always unless told otherwise.0.3.x → 0.4.0) needs explicit user permission. Never bump minor on own. Suggest: "This might warrant 0.4.0 — want minor?" Wait for approval../scripts/version.sh 0.3.X # bump all package.json + Cargo.toml
# REQUIRED for any user-visible release: write the notes file BEFORE
# tagging. CI reads `.github/release-notes/<version>.md` verbatim and
# uses it as the GitHub release body. Skip only for trivial hotfixes
# (CI then auto-generates from conventional-commit subjects, which is
# weak signal for end users). See `.github/release-notes/README.md`
# for what good notes look like + an example at `.../0.4.0.md`.
$EDITOR .github/release-notes/0.3.X.md
git add -A && git commit -m "release: v0.3.X"
git tag v0.3.X
git push origin main --tags
GH Actions (.github/workflows/release.yml) takes over:
qaio-engine for BOTH aarch64-apple-darwin AND x86_64-apple-darwin--target universal-apple-darwin (one fat .app)$APPLE_SIGNING_IDENTITY).app w/ Apple.dmglatest.json w/ darwin-aarch64* AND darwin-x86_64* keysOne DMG covers Apple Silicon + Intel. See knowledge-base/production-infra.md → "macOS Universal".
Duration: ~15-20 min (2-arch compile).
After CI: the release stays as a draft. Stop there. The user reviews the draft and clicks "Publish" themselves. Do NOT run gh release edit --draft=false or otherwise auto-publish — publishing is the user's call, every time.
cargo check --workspace && cd app && pnpm tsc --noEmitmain./scripts/version.sh 0.3.X (patch default).github/release-notes/0.3.X.md — narrative, not a commit dump. Cover: what changed for the user, before-you-upgrade caveats (always include the macOS drag-install reminder), known limitations. Pattern from .github/release-notes/0.4.0.md. Skip only for trivial hotfixes.git add -A && git commit -m "release: v0.3.X"git tag v0.3.X && git push origin main --tagsgithub.com/getqaio/qaio/actionsgh run view <id> --log-failed, fix, commit. Re-tag = git tag -d v0.3.X && git push origin :refs/tags/v0.3.X, then re-tag + push.gh release edit --draft=false is the user's call. Publishing flips on auto-update for every installed Qaio, so it's never auto-pilot../scripts/version.sh 0.2.0
bundle_dmg.sh failed — flaky CI runner. gh run rerun <id>.env!() added. Add secret to GitHub AND workflow YAML.pnpm tsc --noEmit locally BEFORE tagging.See knowledge-base/production-infra.md for full table. Short version: APPLE_SIGNING_IDENTITY, APPLE_API_KEY, APPLE_API_KEY_PATH, APPLE_API_ISSUER, TAURI_SIGNING_PRIVATE_KEY, TAURI_SIGNING_PRIVATE_KEY_PASSWORD, POSTHOG_KEY, POSTHOG_HOST, SUPABASE_URL, SUPABASE_ANON_KEY, SENTRY_DSN. CI also APPLE_CERTIFICATE + APPLE_CERTIFICATE_PASSWORD.
Never hardcode. option_env!() in Rust, env vars in CI.
Fallback to manual build → /build-app-local.