メニュー
Run static checks and high-level validation before a production push in the Inline repo. Use when asked to run checks, verify correctness, or do pre-push/pre-release validation across server/web/admin/apple/cli/proto changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | run-checks |
| description | Run static checks and high-level validation before a production push in the Inline repo. Use when asked to run checks, verify correctness, or do pre-push/pre-release validation across server/web/admin/apple/cli/proto changes. |
Run the minimal set of static checks and targeted builds/tests based on what changed. Prefer fast, focused checks and confirm with the user before long-running steps.
Run git status -sb and git diff --name-only. Group changes by top-level area:
server/web/admin/apple/InlineKitapple/InlineUIapple/InlineIOSapple/InlineMaccli/proto/If only docs or comments changed, report that checks are optional and ask whether to skip.
If proto/ changed, run bun run generate:proto from repo root and include generated diffs.
If dependencies changed, run the relevant install/build for that stack:
bun installcargo fetch (or rely on cargo test/check)swift build in the affected package directoryRun only what maps to the touched areas.
Backend (server/):
cd server && bun run typecheckcd server && bun run lintcd server && bun test (prefer targeted tests when possible)Web (web/):
cd web && bun run typecheckcd web && bun run build only when explicitly requested or required for release validationAdmin (admin/):
cd admin && bun run typecheckCLI (cli/ or protocol changes):
cd cli && cargo test for full validationcd cli && cargo check if a fast static check is sufficientSwift packages:
cd apple/InlineKit && swift build (run swift test if tests were modified)cd apple/InlineUI && swift buildApps:
apple/InlineIOS or apple/InlineMac, do not run full app builds. Ask the user to run xcodebuild locally if needed.Summarize what ran, what passed/failed, and what was skipped with reasons. For failures, include the first actionable error and the next recommended step.
Safely clear a dirty Inline repo worktree by inspecting uncommitted changes, classifying them as safe to commit, review-needed, blocked, or discard candidates, running focused validation, making scoped commits, and asking before destructive cleanup. Use when the user asks to clear the worktree, clean up WIP, commit what is safe, decide what needs Mo review, or update the repository-specific rules for what can be committed versus blocked.
Use when writing, reviewing, or modernizing Swift code that touches Observation, SwiftUI model data, UIKit/AppKit automatic observation tracking, SwiftUI interoperability with UIKit/AppKit, or Apple APIs gated by iOS/macOS versions. Read this before adopting @Observable, migrating ObservableObject code, using new UIKit/AppKit lifecycle tracking, adding SwiftUI to existing UIKit/AppKit apps, or checking whether an iOS 18/macOS 15 or iOS 26/macOS 26 API is safe for the current deployment target.
Review local app/code changes after implementation and produce a concise technical handoff. Use when the user asks for a review, risk assessment, tradeoff check, "what should I review", "give me snippets", or a high-level impact summary after changes that affect multiple app areas, UX, behavior, complexity, tech debt, or bug risk.
Modernize existing Swift test suites by migrating XCTest to Swift Testing or improving current Swift Testing structure. Use when asked to modernize, update, migrate, supercharge, or convert tests. Do not use for writing new tests from scratch, XCTest-only questions, test result review, test running, coverage updates for new functionality, debugging failures without a migration request, or XCUI UI automation tests.
Safely sync local commits with remote by rebasing onto origin/main and then push, following a GitHub Desktop-style flow. Use when asked to push/sync a branch, reconcile local and remote state, resolve rebase conflicts, run targeted tests or typechecks, and push only if checks pass.
Explain and use the Inline CLI (`inline`) for authentication, chats, users, spaces, messages, search, bots, typing, notifications, tasks, schema, attachments, downloads, JSON output, and configuration. Use when asked how to use the Inline CLI or its commands, flags, outputs, or workflows.